Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Kikkerland Frog Cable Ties

tds_purchase_m_kikkerland_frog_cable_ties
Read-onlyIdempotent

Recorded model Frog Cable Ties. 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>",
      "desktopWidthCm": "<desktopWidthCm>",
      "productWidthCm": "<productWidthCm>",
      "leftMarginCm": "<leftMarginCm>",
      "rightMarginCm": "<rightMarginCm>"
    },
    "name": "tds_purchase_m_kikkerland_frog_cable_ties"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

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?

The annotations already establish that this is a safe read-only, idempotent operation, so the description does not need to restate those traits. However, it adds no behavioral context about what the clearance planning result contains, how measurements are interpreted, or any validation behavior beyond the input schema.

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?

The description is short and front-loaded, but the first sentence is a fragment that lacks a clear action. The remaining sentences are efficient but too sparse to make the definition self-explanatory.

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 read-only planning tool with five required numeric parameters, no output schema, and no parameter descriptions, the description is incomplete. An agent can guess that it plans clearance for a specific product variant, but it lacks enough detail to know how to map measurements or what the tool will produce.

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?

With 0% schema description coverage and five required parameters, the description must carry the burden of explaining parameter meaning. It vaguely links offeredModel to the seller's model field and measurements to the exact variant, but it does not explain desktopWidthCm, productWidthCm, leftMarginCm, or rightMarginCm individually.

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 Frog Cable Ties,' which restates the product name rather than stating a clear action. The title mentions 'Plan working clearance,' but the description itself never says what the tool computes or returns, so an agent must infer the purpose 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?

It gives limited input guidance: use the seller's model field or exact variant name and use measurements for the exact variant including required clearances. It does not explain when to use this tool versus the many sibling product tools or what conditions make it appropriate.

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.