Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Yamazaki Tosca Pen + Desk Organizer — Large

tds_purchase_a16
Read-onlyIdempotent

Recorded model Tosca Pen + Desk Organizer Large. Use the seller’s model field or exact variant name. Use measurements for the exact variant, including required clearances.

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>",
      "desktopWidthCm": "<desktopWidthCm>",
      "productWidthCm": "<productWidthCm>",
      "leftMarginCm": "<leftMarginCm>",
      "rightMarginCm": "<rightMarginCm>"
    },
    "name": "tds_purchase_a16"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds only that a specific recorded model/variant must be matched; it says nothing about what the tool computes, what it returns, or how mismatched variants or oversized measurements are handled.

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 with no padding, but the first sentence largely restates the title and product name, and the remaining guidance is fragmented rather than front-loading what the tool does. Some waste, but not verbose.

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 tool with five fully required, undocumented parameters, no output schema, and a non-obvious clearance computation, the description is too thin — it never explains the calculation, the returned result, or which measurements must correspond to which variant dimension. Only the variant-matching requirement is communicated.

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 numeric/string parameters, so the description must carry the load. It touches offeredModel (seller's model field or exact variant name) and gestures at the measurement parameters ('including required clearances'), but never distinguishes desktopWidthCm, productWidthCm, leftMarginCm and rightMarginCm or explains the clearance concept the margins represent.

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 the specific product (Yamazaki Tosca Pen + Desk Organizer, Large) and hints at measurement/clearance use, but never states the verb — whether it records a purchase, computes fit, or validates dimensions. The action only becomes inferable from the title 'Plan working clearance'. An agent can tell it is product-specific but not what it actually performs.

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?

It gives input guidance ('use the seller's model field or exact variant name', 'measurements for the exact variant'), but no when-to-use versus when-not-to-use guidance and no mention of alternatives among the many sibling purchase tools. Nothing tells the agent when this tool is the right choice over a generic organizer tool.

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.