Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Twelve South CableStay Slate

tds_purchase_m_twelve_south_cablestay_slate
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered structurally. The description adds that the tool performs arithmetic comparison rather than retrieval, but says nothing about what the computation yields or how the result is presented, and the voltage/connector checklist is dangling since no such parameters exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences with no padding beyond the opening fragment "Recorded model CableStay Slate," which contributes little. The core purpose sentence is placed early enough to orient the reader.

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, all-required arithmetic tool with no output schema, the description should clarify the computation and what the caller gets back. It leaves reservedWatts undefined and gives no indication of the result shape (e.g., margin or pass/fail), so an agent cannot predict the outcome of a call.

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 coverage is 0%, so the description must carry the load. It maps "declared continuous allowance" to continuousBudgetW, "provided device loads" to primaryDeviceW/otherDevicesW, and gives format guidance for offeredModel, but reservedWatts is never explained and no units or interpretation guidance is given for the watt fields.

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 sentence "This arithmetic compares a declared continuous allowance with provided device loads" does pin down a computation (budget vs. load arithmetic), which is more than a restatement of the name. But the opener "Recorded model CableStay Slate" is cryptic filler and nothing distinguishes this tool from the many sibling variant tools beyond the embedded product 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 input-format advice rather than when-to-use guidance, and no alternative tool or when-not condition is named. The closing "Check voltage, connectors, per-port limits and the setup guide" is generic advice with no stated condition that selects this 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.