Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · Household move supplies

tds_budget_moving_arrivals
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. Household move supplies. Backup packaging 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>",
      "materialsReserveCents": "<materialsReserveCents>"
    },
    "name": "tds_budget_moving_arrivals"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
materialsReserveCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds the calculation sequence (reserve, subtract commitments, compute whole units), but it leaves the exact formula and return value ambiguous, and 'named cost' is unclear.

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?

Very short, but the second and third sentences are disconnected fragments ('Household move supplies.' 'Backup packaging reserve (cents).') rather than integrated structure. It is not bloated, but clarity suffers from the telegraphic style.

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 calculation tool with four required params, no output schema, and 0% schema coverage, the description is incomplete: it does not state the return value precisely, rounding/floor behavior, or how the reserve and commitments interact. The formula sketch is useful but not sufficient.

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?

Schema description coverage is 0%, so the description must define all four required integers. It hints at commitments, cost, and a packaging reserve, but never explicitly maps budgetCents, committedCents, costPerUnitCents, and materialsReserveCents, leaving the agent to guess.

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?

States a specific calculation ('calculate whole affordable units') and the domain ('Household move supplies'), so the agent can identify it as a budget calculator rather than a purchase or handoff tool. It does not explicitly differentiate from the many other tds_budget_* siblings.

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?

Provides no when-to-use or when-not-to-use guidance and names no alternative. 'Household move supplies' is a domain label, not a routing rule.

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.