Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · A display shelf purchase

tds_budget_display_shelves
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. A display shelf purchase. Mounting hardware 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>",
      "mountingBudgetCents": "<mountingBudgetCents>"
    },
    "name": "tds_budget_display_shelves"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
mountingBudgetCentsYes

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?

Annotations already establish that this is a read-only, idempotent, non-destructive calculation. The description adds some behavioral context by outlining the arithmetic sequence—reserve, subtract commitments, calculate whole units—but it does not explain rounding, output format, or edge-case behavior.

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?

The description is short and free of bloat, but it is fragmented and cryptic. 'Reserve the named cost' is not front-loaded with a clear subject, and the two sentence fragments ('A display shelf purchase.' and 'Mounting hardware reserve (cents).') add ambiguity rather than clarity.

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 calculator with no output schema and no parameter descriptions, the description is substantially incomplete. It does not fully explain what each input means, how the calculation handles the mounting reserve, or what exact return value the agent should expect.

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 parameters. It references 'commitments' and 'Mounting hardware reserve (cents)' and implies a per-unit cost, but it does not clearly map budgetCents, committedCents, costPerUnitCents, and mountingBudgetCents to their roles or clarify how they combine.

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 outlines a calculation: reserve a cost, subtract commitments, and compute whole affordable units. However, 'the named cost' is vague and the tool is not clearly distinguished from the many sibling budget calculators, leaving the agent to infer its exact scope from the title and parameter names.

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 explicit guidance on when to use this tool versus alternatives such as tds_budget_art_frame or tds_budget_binder_covers. The only implied context is 'A display shelf purchase,' with no exclusions or decision criteria.

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.