promptspend
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 |
|---|---|
| get_priceA | List price for one LLM in USD per million tokens, with its source and last-confirmed date. Returns disputed=true when two sources disagree, and close matches when the model is unknown. To cost a workload, use estimate_cost. |
| estimate_costA | What a described workload actually costs per month on each model. Accounts for conversation history compounding, cache writes, long-context tiers and reasoning tokens. Use this instead of multiplying prices by hand. |
| find_cheaperA | Cheaper models that score at or above the given one on capability, costed on the same workload. Returns candidates to test, not a recommendation. |
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 3 tools
Each tool has a clearly distinct role: raw price lookup, workload-based cost estimation, and cheaper alternative discovery. The descriptions explicitly cross-reference each other to prevent confusion, especially get_price vs estimate_cost.
All three tools follow a consistent verb_noun snake_case pattern: get_price, estimate_cost, find_cheaper. The naming is predictable and easy to scan.
Three tools is a well-scoped set for an LLM pricing/cost-estimation server. Each tool earns its place by covering a distinct step in the workflow: price lookup, workload costing, and alternative comparison.
The core lifecycle is covered: inspect prices, estimate real workload costs, and find cheaper capable alternatives. A minor gap is the absence of a list/browse operation for discovering available models, though get_price offers close matches for unknown models.