Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Keychron BM25 Kabellose Maus

tds_purchase_m_keychron_keychron_bm25_wireless_mouse
Read-onlyIdempotent

Recorded model BM25 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_bm25_wireless_mouse"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 behavior, so the safety profile is covered. The description adds that the tool performs a local arithmetic comparison, reinforcing that nothing external is touched, but it says nothing about the result shape, edge cases (e.g. negative headroom), or failure behavior.

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?

It is short, but the structure is disjointed: the leading product-label sentence repeats the name and adds no actionable information, and the actual function appears third. Tightening to lead with what the computation does would make every sentence earn its place.

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?

This is a five-parameter arithmetic tool with no output schema and no parameter descriptions, so the description must explain both inputs and the returned comparison. It gestures at the computation but never defines the formula or what the result represents (headroom in watts? a pass/fail verdict), leaving an agent unable to interpret the call's outcome confidently.

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 numeric parameters, so the description carries the full burden. It only loosely maps meanings — "seller's model field or exact variant name" to offeredModel, "continuous allowance" to continuousBudgetW, "device loads" to primaryDeviceW/otherDevicesW — and never mentions reservedWatts or the units/limits of the watt fields, leaving real ambiguity.

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 core purpose is buried mid-description: "This arithmetic compares a declared continuous allowance with provided device loads." That is a specific statement, but the opener ("Recorded model BM25 Kabellose Maus") reads like a product label rather than a tool action, and the buyer/compare framing implied by the name is never reconciled with the power-arithmetic function. An agent can guess it computes a power-budget check but not cleanly what it does relative to its purchase-comparison siblings.

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 routing advice is "Use the seller's model field or exact variant name," which is a parameter hint rather than a when-to-use rule. "Check voltage, connectors, per-port limits and the setup guide" is generic caution, not a condition for selecting this tool over the many sibling product tools, and no alternative is named or excluded.

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.