Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Stasher Touch-Up Bag

tds_purchase_m_stasher_beauty_touch_up_bag
Read-onlyIdempotent

Recorded model Touch-Up 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_beauty_touch_up_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, and destructiveHint=false, so the safety profile is covered and the bar is lower. Still, the description says nothing about what the call produces (a fit verdict?) or how the four measurements are combined, which is the substantive behavior an agent would want disclosed.

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 bloat and no repetition, which is structurally fine. However, the opening sentence is effectively dead weight since it conveys no actionable information, so brevity comes at the cost of content rather than from efficiency.

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 mandatory numeric inputs, no schema descriptions, and no output schema, the description needs to explain the fit computation and the meaning of each clearance. It leaves both the operation and the result undefined, so an agent cannot confidently map inputs to a correct call.

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 coverage is 0% across five required parameters, so the description must carry the load. It clarifies offeredModel (seller's model field or exact variant name) and hints that measurements must be variant-specific including clearances, but never distinguishes shelfDepthCm, productDepthCm, useClearanceCm, and frontClearanceCm, nor their units and roles.

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 Touch-Up Bag" restates the product name in the tool name and supplies no verb describing what the tool does. The title suggests a space/fit check, but the description never states that it evaluates whether the bag fits given shelf, product, and clearance measurements, so an agent must guess the operation from the 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?

"Use the seller's model field or exact variant name" is input-format guidance, not a when-to-use rule. There is no statement of when this fit-check applies versus the many sibling Stasher variant tools, and no prerequisites or exclusions.

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.