mcp-flatratemath
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cost_per_requestA | Price one way of paying for software work as total cost per delivered request. mode: bid (one-time fixed price), salary (monthly cost of a hire, fully loaded), or flat (monthly subscription fee). months is how long the work stays alive; requests is how many discrete work items you expect to submit. |
| compare_lanesB | Rank up to three payment lanes (bid, salary, flat) by cost per delivered request on one sheet. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have mostly distinct purposes: cost_per_request prices one payment lane, while compare_lanes ranks up to three lanes side by side. There is some inherent overlap because compare_lanes presumably repeats the single-lane calculation, but the boundary between single-lane pricing and multi-lane comparison is clear enough for an agent.
Both names use snake_case, but the convention is mixed: compare_lanes follows a verb_noun pattern, while cost_per_request is a noun phrase. The meanings remain readable, but the set is not fully consistent.
Two tools is thin for a standalone pricing server, though the domain is narrow enough that a single-lane calculator plus a comparison tool covers the main need. It sits at the borderline of being under-scoped.
The surface covers pricing one lane and comparing up to three lanes, which addresses the core flat-rate math use case. Minor gaps might include scenario/sensitivity analysis or saving/exporting results, but agents can work around those limitations.