Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Stasher Go Bag

tds_purchase_m_stasher_reusable_silicone_go_bag
Read-onlyIdempotent

Recorded model Go Bag. 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_stasher_reusable_silicone_go_bag"
  }
}

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, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that the description adds nothing: no indication of what the call produces (a fit verdict?), how clearance is evaluated, or what happens with a non-matching variant.

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 filler, which is appropriately sized. However, the opening sentence is vague filler rather than a front-loaded statement of the tool's action, so brevity does not translate into clarity.

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 tool with no output schema and no parameter documentation, so the description has to do more work than it does. The critical gaps — units, how fit is determined, and what the response represents — are unaddressed, making correct invocation largely guesswork.

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%, so the description must carry parameter meaning. It gives partial guidance for offeredModel (seller's model field or exact variant name) and gestures at "measurements ... including required clearances", but does not distinguish shelfDepthCm from productDepthCm or useClearanceCm from frontClearanceCm, and never states the unit.

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?

"Recorded model Go Bag" essentially restates the tool name and title without a verb or outcome. It never says the tool checks whether a specific Stasher Go Bag variant fits a shelf given product depth and clearances, which is only inferable from the title and parameter names.

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?

There is one usage instruction — use the seller's model field or exact variant name — but no statement of when to use this tool versus the many sibling bag tools, nor any prerequisites or exclusions. The agent is left to infer selection from names alone.

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.