Skip to main content
Glama

RipSeek

What a budget usually returns

estimate_budget
Read-onlyIdempotent

Estimates what spending a budget on one pack usually returns: how many packs it buys, the average insured value pulled, the average cash back if every card is sold back, the average result, and the chance of at least one Rare or Epic. Use it when the user asks what to expect from spending an amount, or whether a pack is worth it; use get_pack for the pack's odds and top cards. Read-only; honest averages from Collector Crypt's live odds, not a promise, and real results swing a lot with few packs.

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": {
      "code": "<code>",
      "budget": "<budget>"
    },
    "name": "estimate_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesPack code from list_packs, lowercase, e.g. pokemon_50, onepiece_250, soccer_100.
budgetYesBudget in US$, e.g. 250. Must cover at least one pack.

Output Schema

NameRequiredDescriptionDefault
noteNo
packYes
packsYes
play_safeNo
spent_usdNo
chance_at_least_one_epic_pctNo
average_result_if_all_sold_usdNo
average_insured_value_pulled_usdNo
average_cash_back_if_all_sold_usdNo
chance_at_least_one_rare_or_epic_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile needs no restating. The description adds genuinely new context: the numbers come from Collector Crypt's live odds, they are averages rather than promises, and results 'swing a lot with few packs' — a variance caveat that meaningfully shapes interpretation. It stops short of stating computational cost or latency, which keeps it from a 5.

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?

The purpose and its enumerated outputs are front-loaded, followed by usage guidance and a caveat, in three compact clauses with no filler. The output enumeration is dense but each item earns its place because it tells the agent what to report back; only minor tightening would improve flow.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and the description still conveys the analysis type (averages, probability of a hit), the data source, the variance caveat, and the sibling to prefer for raw odds. For a two-parameter read-only estimator nothing an agent needs to select or call it correctly is missing.

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 description coverage is 100%, so both parameters are already documented in the schema, including the pack-code format, the US$ budget example, and the 'must cover at least one pack' constraint. The description adds no additional parameter-level meaning, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb ('Estimates') and resource ('what spending a budget on one pack usually returns'), then enumerates the exact outputs: packs bought, average insured value, average cash back, average result, and chance of at least one Rare or Epic. An agent can distinguish it from get_pack, which returns odds and top cards, without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions ('when the user asks what to expect from spending an amount, or whether a pack is worth it') and names the alternative to use for a different question ('use get_pack for the pack's odds and top cards'). Both when-to-use and when-to-use-something-else are covered.

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