Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Twelve South CableStay Dune

tds_purchase_m_twelve_south_cablestay
Read-onlyIdempotent

Recorded model CableStay Dune. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, and the description is consistent with that by framing the tool as pure arithmetic on supplied numbers. It adds little beyond the annotations, however: no statement of what the computed result means, whether inputs are validated against the recorded model, or what happens when provided wattages exceed the allowance. The closing "check voltage, connectors, per-port limits" implies checks that are not evidenced by the five numeric/string parameters.

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 the calculation intent arrives by the third sentence, so it is not padded. But the opening is a bare product-name restatement that earns nothing, and the final sentence bundles three unrelated advisories, muddying rather than sharpening the structure.

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 computational tool with no output schema and five undocumented required parameters, the description never says what is returned (headroom in watts, a boolean verdict, a breakdown) or how the result should be interpreted. Given the required reservedWatts input is unexplained and there is no output schema to fall back on, an agent cannot confidently predict the response.

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 must carry the semantics, and it does partially: "declared continuous allowance" maps to continuousBudgetW, "provided device loads" maps to primaryDeviceW and otherDevicesW, and "seller's model field or exact variant name" maps to offeredModel. reservedWatts — required and clearly material to a headroom calculation — is never explained, and no units (watts) or expected value ranges are given.

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?

"This arithmetic compares a declared continuous allowance with provided device loads" conveys that the tool performs a wattage-budget calculation, but the verb is abstract and the opening sentence ("Recorded model CableStay Dune") restates the title rather than stating an action. An agent can infer this is the Dune-variant of a per-product power check, but nothing explicitly distinguishes it from the fuchsia/slate siblings beyond the model name.

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 the only selection-relevant instruction and it concerns a parameter value, not when to call this tool. There is no statement of prerequisites, when-not-to-use, or how it relates to any alternative. "Check voltage, connectors, per-port limits and the setup guide" reads as advice to the caller rather than usage guidance for the 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.