Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Fellow Old Crow Cuppa Joe

tds_purchase_m_fellow_old_crow_cuppa_joe
Read-onlyIdempotent

Recorded model Old Crow Cuppa Joe. 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_fellow_old_crow_cuppa_joe"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

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 establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds only input requirements—exact variant and clearances—and does not explain what the check returns, how measurements are compared, or what happens on a mismatch; no output schema fills that gap.

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?

It is short, but the opening sentence is a redundant model restatement and the description is front-loaded with data-entry rules rather than purpose. The sentences are compact, yet the structure makes the agent work to infer the operation.

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-parameter fit-checking tool with no output schema and no schema descriptions, the definition is incomplete: it omits the actual check outcome, units, and parameter-level meaning. The annotations cover safety, but the description does not complete the operational picture.

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% for five required parameters. The description gives useful guidance for offeredModel ('seller’s model field or exact variant name') and generically mentions measurements and clearances, but it does not define shelfDepthCm, productDepthCm, useClearanceCm, or frontClearanceCm, nor units or how they relate.

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 title names a 'kitchen space' check and the description names the specific recorded model, but the description itself never states the verb or outcome, such as whether the item fits. It identifies the resource but leaves the action implicit, so an agent must infer purpose from the title.

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?

The description tells the caller to use the seller's model field or exact variant name and to use measurements including required clearances, but it gives no when-to-use versus when-not-to-use guidance. It also does not mention alternatives such as tds_quote_storage_space; usage is implied by the title rather than explained.

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.