Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Fellow Carter Slide Mug

tds_purchase_m_fellow_carter_slide_mug
Read-onlyIdempotent

Recorded model Carter Slide 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_fellow_carter_slide_mug"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds little beyond input guidance: it does not explain what the 'check' actually validates, what result is returned, or what happens when clearances fail, despite there being no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded enough to scan quickly, with no redundant sentences. The opening phrase 'Recorded model Carter Slide Mug' is slightly awkward, but overall the structure is efficient.

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 check tool with five required measurement parameters and no output schema, the definition should explain what is being checked and what the result means. The description leaves the fit/clearance logic, return behavior, and individual measurement semantics largely unspecified.

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 needs to carry parameter meaning. It partially does by saying to use the seller's model field or exact variant name for the model and to use exact-variant measurements including required clearances, but it does not clarify each depth and clearance parameter individually.

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 supplies the verb 'Check kitchen space' and names the exact product, but the description itself only says 'Recorded model Carter Slide Mug' without explicitly stating that it checks fit or clearance. The product-specific name distinguishes it from most siblings, but the action is inferred rather than stated in the description.

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 gives input guidance about using the seller's model field or exact variant name, but does not say when to use this tool versus alternatives such as quote_storage_space or other product-specific tools. It also gives no exclusions or conditions for choosing this 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.