Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Anker 317 Ladegerät (100W)

tds_purchase_m_anker_b2672
Read-onlyIdempotent

Recorded model 317 Ladegerät (100W). 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_anker_b2672"
  }
}

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?

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior. The description adds that this is an arithmetic comparison using a declared budget and supplied loads, rather than a live product lookup, but it does not explain the result format or error behavior, and its checklist advice is not reflected in 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.

Conciseness4/5

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

The description is short and front-loads the model and core arithmetic. However, the opening 'Recorded model...' phrasing is somewhat cryptic, and the closing checklist is advisory rather than directly tied to the tool’s inputs or outputs.

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?

With five required parameters and no schema descriptions or output schema, the description should define parameter roles and the result more fully. It instead references voltage, connectors, per-port limits and the setup guide, none of which appear in the input schema, leaving significant gaps for correct invocation.

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%, so the description must carry parameter meaning and only partially does. It maps offeredModel to the seller’s model field/exact variant and implies continuousBudgetW and device loads, but it does not explain reservedWatts or clearly distinguish primaryDeviceW from otherDevicesW.

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?

States a specific calculation: comparing a declared continuous power allowance with provided device loads, and identifies the model as Anker 317 Ladegerät (100W). It distinguishes itself as an arithmetic comparison rather than a product lookup, though it does not explicitly compare itself to sibling 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?

Provides some input guidance by saying to use the seller’s model field or exact variant name, and advises checking voltage, connectors, per-port limits and the setup guide. However, it gives no explicit when-to-use versus alternatives guidance and no clear preconditions or exclusions.

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.