Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Anker Prime USB-C to USB-C Cable (240W, Upcycled-Braided)

tds_purchase_b20
Read-onlyIdempotent

Recorded model A88E2. 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_b20"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive and closed-world behavior. The description adds useful context that this is an arithmetic comparison limited to power allowance versus device loads and that other compatibility factors must be checked separately, but it does not explain output format, thresholds or error behavior.

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?

The description is short and mostly front-loaded with the model requirement and the core arithmetic purpose. It is concise with little wasted wording, though the opening 'Recorded model A88E2' is somewhat cryptic and the core purpose could appear earlier.

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-required-parameter calculation tool with no output schema and no schema descriptions, the definition leaves important gaps. It does not explain the return value, reservedWatts, or the precise power-budget formula, so an agent must infer too much from parameter names alone.

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% across five required parameters, so the description must carry the explanatory burden. It clarifies offeredModel and loosely maps continuousBudgetW and device-load parameters to the comparison, but it does not explain reservedWatts, aggregation semantics for otherDevicesW, units, or how the values are combined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific comparison: it compares a declared continuous power allowance with provided device loads, and it identifies the recorded model A88E2. This is a clear verb-and-resource purpose, though it does not explicitly distinguish itself from the sibling purchase-oriented tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives implied usage guidance by describing the arithmetic comparison and by instructing the caller to use the seller's model field or exact variant name and to check voltage, connectors, per-port limits and the setup guide. However, it does not say when to use this tool versus alternatives or when not to use it.

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.