Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Hario NOTE Mug

tds_purchase_m_hario_note_mug
Read-onlyIdempotent

Recorded model NOTE Mug. 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>",
      "shelfDepthCm": "<shelfDepthCm>",
      "productDepthCm": "<productDepthCm>",
      "useClearanceCm": "<useClearanceCm>",
      "frontClearanceCm": "<frontClearanceCm>"
    },
    "name": "tds_purchase_m_hario_note_mug"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

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, closed-world, so the safety profile is covered. The description adds nothing about what is computed, how clearances are applied against shelf depth, or what the caller receives in the absence of an output schema — the tool's actual behavior remains opaque.

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 text is short with no filler sentences, so length is not a problem. However, the opening sentence conveys nothing and the useful input guidance is buried in the middle, so the definition is not front-loaded around the tool's 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?

This is a five-parameter, all-required computation with no output schema and no per-field schema documentation, which puts the full explanatory burden on three short sentences. Given that complexity, the description is materially incomplete: it neither states the computation nor defines the measurement inputs well enough to guarantee a correct call.

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 must carry the burden and largely fails. It clarifies only that offeredModel should be the seller's model name or exact variant and that the clearance values are 'required clearances'; it never distinguishes shelfDepthCm from productDepthCm, states units, or explains how useClearanceCm differs from frontClearanceCm.

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 an action verb or outcome: it opens with 'Recorded model NOTE Mug,' which essentially restates the tool name, and only mentions which inputs to supply. An agent cannot tell from the text whether the tool returns a fit/no-fit verdict, a storage recommendation, or a lookup record, even though the title hints at 'Check kitchen space.'

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-selection advice, not when-to-use guidance. There is no statement of when this fit-check applies versus a sibling like tds_quote_storage_space, nor any exclusion or precondition for invoking it.

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.