Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · soundcore Liberty Air 2 Pro

tds_purchase_m_soundcore_a3951051
Read-onlyIdempotent

Recorded model Liberty Air 2 Pro. 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_soundcore_a3951051"
  }
}

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful scope limitation by warning that voltage, connectors, and per-port limits are NOT modeled and must be checked against the setup guide, but it never says what the computation returns or how to interpret the result.

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?

Three short sentences with no padding, but they are clipped to the point of ambiguity, and the opening model-reference sentence is the least useful information yet occupies the front-loaded position where the actual purpose should sit.

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, fully-required tool with no output schema and zero schema description coverage, the description should explain what the comparison produces and what reservedWatts means. It covers the model-matching rule and out-of-scope physical factors but leaves the result semantics entirely unexplained.

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% across five required parameters, so the description must compensate. It clarifies offeredModel (use the seller's model field or exact variant name) and maps 'declared continuous allowance' to continuousBudgetW and 'provided device loads' to primaryDeviceW/otherDevicesW, but reservedWatts and the expected units/magnitudes of the load values are never addressed.

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 states the operation as arithmetic that 'compares a declared continuous allowance with provided device loads', which is a specific verb-plus-resource framing. However, the leading sentence 'Recorded model Liberty Air 2 Pro' describes a product reference rather than the action, and the title's 'Compare power allowance' is not clearly reconciled with the purchase-oriented tool name, leaving the agent to infer exactly what this tool computes.

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?

The only directive is 'Use the seller's model field or exact variant name' plus a caution to 'check voltage, connectors, per-port limits and the setup guide'. That is input validation and caveat advice, not guidance on when to select this tool over the many sibling purchase tools or when it is inapplicable. No alternative is named.

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.