Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto HIBI fork 160mm

tds_purchase_m_kinto_27105
Read-onlyIdempotent

Recorded model HIBI fork 160mm. 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_kinto_27105"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/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 structurally. The description adds one real constraint — measurements must correspond to the exact variant and must include required clearances — but says nothing about what the check returns or how pass/fail is decided, so it adds only modest context.

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, which is good, but the lead sentence ("Recorded model HIBI fork 160mm") carries almost no information and is not front-loaded with the tool's action. The remaining two sentences are terse instructions attached to parameters rather than a structured 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?

With five required numeric inputs, no output schema, and no annotations explaining results, the description leaves large gaps: an agent cannot tell what verdict or data comes back, what units or measurement basis apply, or how clearance values should be derived. It is not adequate for a computation-style tool of this complexity.

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 parameters, so the description must carry the burden and does not. It only loosely gestures at offeredModel ("seller's model field or exact variant name") and at the four measurement/clearance fields collectively, without explaining the distinction between shelf depth, product depth, use clearance and front clearance, or where those clearance values should be sourced.

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 opens with "Recorded model HIBI fork 160mm," which restates the product in the title rather than stating what the tool does. There is no verb such as "check" or "verify fit"; the fit-checking intent must be inferred from "required clearances," and no sibling (e.g. tds_quote_storage_space) is mentioned for contrast.

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 guidance on filling a parameter, not on when to invoke this tool versus the storage-space quote tool or the numerous other purchase siblings. No preconditions, exclusions, or alternatives are given.

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.