Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · Convention purchases

tds_budget_convention_trips
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. Convention purchases. Travel reserve (cents).

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": {
      "budgetCents": "<budgetCents>",
      "committedCents": "<committedCents>",
      "costPerUnitCents": "<costPerUnitCents>",
      "tripBudgetReserveCents": "<tripBudgetReserveCents>"
    },
    "name": "tds_budget_convention_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
tripBudgetReserveCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, so the description needn't restate safety. It usefully adds the calculation order and the concept of whole affordable units, but leaves out rounding rules, return format, and failure conditions.

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

Conciseness3/5

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

It is short and avoids filler, but the three sentence fragments are not well structured or front-loaded. The purpose statement is split awkwardly across the algorithm and the trailing 'Travel reserve (cents)' phrase.

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

Completeness2/5

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

For a four-parameter calculation tool with no output schema and no parameter descriptions, the definition is too incomplete. It does not fully explain parameter roles, the output meaning of 'whole affordable units,' or how tripBudgetReserveCents changes the calculation.

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

Parameters2/5

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

With 0% schema description coverage across four required parameters, the description must carry parameter meaning, but it only loosely maps concepts like commitments and travel reserve. It does not clearly identify budgetCents, committedCents, costPerUnitCents, or how the reserve is applied.

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

Purpose3/5

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

The description names a calculation sequence (reserve, subtract commitments, calculate affordable units) and a domain (convention purchases), but the purpose is fragmented and never directly states that it checks remaining purchase budget. It is distinguishable from purchase-order siblings by the budget-calculation framing, though not sharply.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the many sibling budget and purchase tools, and no alternatives or exclusions are named. The phrase 'Convention purchases' provides context but not usage rules.

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.