Skip to main content
Glama

Calculate Budget Stack

calculate_budget_stack
Read-only

Run the OunceScout Smart Budget Stack Calculator to find the optimal physical Gold & Silver bullion stack for a target USD budget at today's lowest live dealer prices.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "budgetUsd": "<budgetUsd>"
    },
    "name": "calculate_budget_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
strategyNoAllocation strategy: 'balanced' (Gold + Silver mix), 'gold' (Gold only), or 'silver' (Silver only).
budgetUsdYesTarget budget in USD (e.g., 1000, 2500, 5000, 10000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and external-dependency framing is covered; the description reinforces the open-world aspect by tying results to 'today's lowest live dealer prices'. It does not disclose how many dealers are considered, freshness/latency of the prices, or what the returned stack looks like — notable gaps given there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the budget target at the fore; efficient and readable. The branded 'OunceScout Smart Budget Stack Calculator' phrasing is mild filler but does not obscure meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, fully documented read-only tool, the description covers the essential purpose, data source, and objective. The main shortfall is that with no output schema it never characterizes the returned allocation (items, quantities, costs), leaving the agent to infer the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters carry inline descriptions including the enum values for 'strategy', so the schema does the heavy lifting. The description only echoes the budget input ('target USD budget') and adds nothing about how strategy selection changes behavior or how fractional budgets are handled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action and deliverable: produce an optimal Gold & Silver bullion stack allocation for a target USD budget using live dealer prices. That is clearly distinct from the sibling tools (price lookups, dealer listings, catalog search), although it never explicitly routes against them by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'for a target USD budget' and 'today's lowest live dealer prices', which tells the agent this is a budget-allocation tool rather than a price-quote tool. There is no explicit when-to-use, when-not-to-use, or named alternative, so guidance remains inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources