Skip to main content
Glama

The Doll Scout Home Tools

Check remaining purchase budget · An offer on a collection

tds_budget_collection_offer
Read-onlyIdempotent

Reserve the named cost, subtract commitments, then calculate whole affordable units. An offer on a collection. Unpacking supplies 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>",
      "unpackingReserveCents": "<unpackingReserveCents>"
    },
    "name": "tds_budget_collection_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetCentsYes
committedCentsYes
costPerUnitCentsYes
unpackingReserveCentsYes

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 that this is a safe, read-only, idempotent, closed-world operation. The description adds a rough sequence of reserve, subtract commitments, and calculate whole units, but it does not explain exact arithmetic, rounding behavior, return shape, or edge cases, and 'Reserve' is ambiguous despite not directly contradicting readOnlyHint.

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, but it is fragmented: 'An offer on a collection' does not earn its place and 'Unpacking supplies reserve (cents)' reads as a stray fragment. It is front-loaded with procedure rather than a clear statement of purpose.

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 read-only calculator with four required numeric inputs and no output schema, the definition should make the calculation and parameter roles clear. The annotations cover safety, but the description leaves key calculation semantics and the expected return value underspecified.

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% and all four parameters are required, so the description must carry parameter meaning. It mentions commitments and an unpacking supplies reserve, but it does not clearly map budgetCents, committedCents, or costPerUnitCents, and 'named cost' is too vague to compensate.

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 indicates a budget calculation ending in 'whole affordable units,' so an agent can infer a calculator. However, it states an internal procedure rather than a clear tool purpose, and 'An offer on a collection' is opaque and does not distinguish it from the many sibling tds_budget_* tools.

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 when-to-use guidance, no prerequisites, no exclusions, and no named alternative or sibling comparison. 'An offer on a collection' provides only a loose domain hint.

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.