Inspiration
I am inspired by many graph makers and calculation engines. I wanted to combine their traits so calculations can be more easily visualized. Calculations with real-life timings to represent the results give the repeating arithmetic operations a practical sense. I was inspired by recurring bank interests, inflations, certain amounts added or deducted from accounts, etc. I was inspired to provide dates from milliseconds to years because real life finances can have even more detailed representations. That's how I was inspired, learning and trying to simplify domestic economic cultures to international ones through different ways. To create this project with WebMCP tools, I was inspired by one of my own projects (created years ago, to automate a website through embedded javascript running engine and creating automated flows and extra UI guiding visuals by a hosted web-app, connecting them with a backend). I found this approach more effective in current times where Users and Agents can operate web-apps together and web-apps functionality is standardized so agents don't have to look for UI clicks or other DOM elements.
What it does
With Time&Dime one can create financial scenarios such as salaries, interests, debt payments, expenses, inflations, etc. with cards. WebMCP allows the agents to create models and perform all the required actions, run tools and return values for users, and Users can also create, edit and perform all the operations on the web-app UI. Users and WebMCP tools working together provide a very effective workspace to create complex financial models.
With WebMCP tools implemented, it becomes easier to provide instructions to agents for creating multi-step financial models with natural text. Wherever nodes can use latest information for correct values then agents can solve this beforehand. All this creates editable UI for users to manually configure their models later.
From the individual card's time, performing the cards' operations (Plus, Minus, Divide, Multiply, Modulus) with card's value/percentage, and with given time limit or till project's duration or end-time, on the above card(s).
How we built it
I am using Vue.js to build this web-app. For design choice and practical user experience I am using a simple flow that I used for years on my older projects, which is cards created vertically or horizontally. Considering simple requirements, I am choosing this instead of implementing vue-flow.
I am using local storage to store projects, nodes and their values and watching the nodes so any change reflects updated object in the local storage.
Initially while working each step, I started implementing WebMCP imperative API tools for core functionalities of the web-app and then after the app had reached a point of being a viable product then I created more imperative API tools for my web-app to support all of the features through Agent.
I used codex 5.6 sol to work through the development step by step, creating custom design of my web-app, implementing states of the project and nodes, creating CRUD for local storage, defining WebMCP imperative API tools to execute functions directly, scaffolding JS files to perform calculations.
Challenges we ran into
Creating calculation engine was taking a lot of time, First try using loops for a bit of complicated multi-operations involving project, hangs up the web-app. So I asked 5.6 sol ultra mode for planning and development, Then a hybrid calculation engine with limits was scaffolded in the JS files.
Then having too much metadata for WebMCP tools was making a limit hit on chatGPT internal browser, So I worked with 5.6 sol's Ultra mode again to work out this issue.
Accomplishments that we're proud of
Time&Dime project is up and running, With its version one, It can visualize many scenarios and create many complicated models. The nodes/cards are extremely customizable. The projects are currently isolated. WebMCP tools are properly working with the web-app. I finally have something at hand which allows me to create graphs of calculations my way!
What we learned
I learned a lot from this hackathon. First I usually try to write 2-3 modules together and sometimes codex overdoes the work and make it more like framework style. But slowly I am learning to tame codex and use lower settings like medium to create only the structure of code that one wants at a time and then performing designing of the whole project modules interconnectivity separately and work on that one by one. If a solution requires code that will turn ambiguous unintentionally (alternative to use open-source/ready-made scripts) then have it separated and validate with custom tests.
I learned more about how I was designing this web-app and how it should turn out. Working with it made me more aware of nuances in flows of economics, which is still relatively small compared with what other kind of deployments exists in this subject throughout other markets.
What's next for Time&Dime
I will work towards adding more features, First will be to use an existing project inside another existing project. Then I will work towards other cooler new features which I have planned to make this web-app more exciting to use.
Built With
- codex
- javascript
- vue
- webmcp
Log in or sign up for Devpost to join the conversation.