Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto CAST AMBER jug 1.2L

tds_purchase_m_kinto_21464
Read-onlyIdempotent

Recorded model CAST AMBER jug 1.2L. 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_21464"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that the description says nothing about what the call produces (a fit verdict? stored record?), what rule compares shelf depth against product depth plus clearances, or what happens when the clearance budget is exceeded.

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?

Two short sentences with no filler, so nothing is wasteful. However, the lead sentence carries no operational information, and the substantive constraints (model field, measurements, clearances) arrive only after the product restatement.

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-required-parameter check with no output schema and no annotated behavior detail, so the description is the only place the evaluation logic could be explained. It omits the fit rule, the return shape, and the units, leaving the agent to guess how the inputs combine.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it partly does: it distinguishes the model identifier from the measurement inputs and flags that clearances are required. It still leaves the distinction between useClearanceCm and frontClearanceCm, and the implied unit convention for the _Cm fields, unexplained.

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 CAST AMBER jug 1.2L', which restates the title's product identity rather than naming an operation. No verb states what the tool actually does (e.g., evaluate whether the jug fits a shelf given depth and clearance inputs), so an agent must infer the purpose from the parameter names alone.

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 sentences 'Use the seller's model field or exact variant name' and 'Use measurements for the exact variant' govern how to fill inputs, not when to select this tool. There is no guidance on when to call it versus siblings such as tds_quote_storage_space, nor any stated precondition or exclusion.

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.