Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Twelve South CableStay Fuchsia

tds_purchase_m_twelve_south_cablestay_fuchsia
Read-onlyIdempotent

Recorded model CableStay Fuchsia. Use the seller’s model field or exact variant name. This arithmetic compares a declared continuous allowance with provided device loads. Check voltage, connectors, per-port limits and the setup guide.

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>",
      "continuousBudgetW": "<continuousBudgetW>",
      "primaryDeviceW": "<primaryDeviceW>",
      "otherDevicesW": "<otherDevicesW>",
      "reservedWatts": "<reservedWatts>"
    },
    "name": "tds_purchase_m_twelve_south_cablestay_fuchsia"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds that this is an arithmetic comparison and lists things to verify, but it does not explain the calculation logic, what the result looks like, or how invalid or inconsistent wattage values are handled.

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 enough to read quickly, but 'Recorded model CableStay Fuchsia' largely repeats the tool name and title, and the caution about voltage, connectors, per-port limits, and the setup guide is underspecified. It is concise but not tightly front-loaded around the core calculation.

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 five-parameter calculation tool with no output schema and no schema parameter descriptions, the description should explain enough for an agent to pass correct values and understand the result. It does not describe the arithmetic relationship, units, constraints, or return value, leaving major gaps despite the annotations covering safety.

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% for five required parameters. The description loosely maps 'declared continuous allowance' to continuousBudgetW and 'provided device loads' to the device-load inputs, and mentions the model field for offeredModel, but reservedWatts is never explained and units or valid relationships among the wattage parameters are not clarified.

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 description says it is an 'arithmetic' that 'compares a declared continuous allowance with provided device loads,' which gives a specific operation and resource. However, it is framed around a recorded product model and never clearly states whether the tool is a catalog lookup, a power-budget calculator, or a purchase helper, so differentiation from the many product-variant siblings remains vague.

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 advises using 'the seller’s model field or exact variant name' and to 'Check voltage, connectors, per-port limits and the setup guide,' but gives no when-to-use condition, no when-not-to-use condition, and no explicit alternative among the many sibling product tools. The guidance is input advice and caveats rather than tool-selection guidance.

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.