Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Keychron BM22 Kabellose Maus

tds_purchase_m_keychron_keychron_bm22_wireless_mouse
Read-onlyIdempotent

Recorded model BM22 Kabellose Maus. 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_keychron_keychron_bm22_wireless_mouse"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, which fits the claim that this is pure arithmetic. The description adds context beyond that — it is a comparison of a declared allowance against supplied loads, and it warns to verify voltage, connectors and per-port limits — but says nothing about units, rounding, what happens if loads exceed the budget, or what the response contains.

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 little filler, and the model-identification instruction is front-loaded. The final sentence mixes unrelated cautions (voltage, connectors, per-port limits, setup guide) into a list that is not obviously relevant to the stated arithmetic, which blurs the message rather than sharpening it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Recomputed for a read-only, no-output-schema arithmetic tool with five undocumented numeric inputs: the definition gives the overall computation and one input-identification rule, but leaves the four wattage parameters' relationships and expected result undefined, so an agent cannot reliably construct or interpret the comparison from the text 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%, so the description must carry all five required parameters, yet it only clarifies offeredModel (use the seller's model field or exact variant name). It never distinguishes continuousBudgetW from primaryDeviceW, otherDevicesW or reservedWatts, nor states whether watts are additive, per-port, or already reserved — the numeric semantics that determine a correct call are missing.

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 does state an action — 'This arithmetic compares a declared continuous allowance with provided device loads' — so the operation is identifiable as a power-budget comparison tied to model BM22. However, the pairing of a wireless mouse product with a power-allowance arithmetic is confusing, and the description never says what the comparison produces or how it differs from the dozens of sibling product tools. Purpose is inferable but not crisp.

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?

'Use the seller's model field or exact variant name' gives concrete guidance for populating offeredModel, and 'Check voltage, connectors, per-port limits and the setup guide' implies a pre-check before trusting the result. There is no statement of when to use this versus a sibling product tool, and no explicit exclusions or prerequisites for the numeric inputs.

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.