Skip to main content
Glama

The Doll Scout Home Tools

Plan materials and spare stock · UHU Patafix White Adhesive Pads

tds_purchase_d24
Read-onlyIdempotent

Recorded model 35211. Use the seller’s model field or exact variant name. Use one consistent unit for the material and checked values for the exact pack or accessory.

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": {
      "offeredModel": "<offeredModel>",
      "projects": "<projects>",
      "amountPerProject": "<amountPerProject>",
      "unitsPerPack": "<unitsPerPack>",
      "sparePercent": "<sparePercent>"
    },
    "name": "tds_purchase_d24"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectsYes
offeredModelYes
sparePercentYes
unitsPerPackYes
amountPerProjectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description adds only a vague directive about consistent units, and says nothing about what the tool computes or returns — critical given there is no output schema to explain the result (e.g. how sparePercent affects the recommendation).

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?

Three short sentences, reasonably front-loaded, and nothing is padded. However, the leading model number is opaque without context and the sentences mix identification with parameter advice rather than building a coherent explanation.

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 five-required-parameter planning tool with no output schema and no annotation coverage of results, the description should explain the computation and the meaning of fields like sparePercent. Instead it leaves the agent guessing what the output represents and how each value is used.

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% across five required parameters, so the description bears the full burden. It clarifies offeredModel (seller's model field or exact variant name) and hints at unitsPerPack/amountPerProject via 'one consistent unit' and 'checked values for the exact pack', but projects and especially sparePercent (0–100) are left entirely undefined.

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

Purpose2/5

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

The description never states a verb or what the tool actually does; 'Recorded model 35211' identifies a variant but is not a purpose statement. Only the title ('Plan materials and spare stock') conveys the action, and the description itself reads as leftover notes rather than a definition of the operation.

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?

'Use the seller's model field or exact variant name' is input guidance, not when-to-use guidance. Nothing indicates when an agent should pick this tool over the many sibling purchase/stock tools, nor what conditions would make it inappropriate.

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.