Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Keychron BM24 Kabellose Maus

tds_purchase_m_keychron_keychron_bm24_wireless_mouse
Read-onlyIdempotent

Recorded model BM24 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_bm24_wireless_mouse"
  }
}

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?

The description is consistent with the annotations (readOnly, idempotent, closed-world) and adds the useful fact that this is pure arithmetic over supplied numbers, implying no persisted state or side effects. It does not disclose the result shape, units, or what happens when the budget is exceeded, so it adds only moderate value beyond the annotation block.

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 outright padding, but the lead line 'Recorded model BM24 Kabellose Maus' is cryptic front-loading, and the closing checklist sentence is vague enough that it reads as filler rather than actionable instruction.

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 numeric tool with no output schema, the description should say what the computed result is and how reservedWatts participates. Instead the agent is left guessing at units, output shape, and the meaning of one required parameter, which is a meaningful completeness gap.

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%, so the description must compensate. It loosely maps 'declared continuous allowance' to continuousBudgetW, 'provided device loads' to primaryDeviceW/otherDevicesW, and clarifies that offeredModel takes the seller's model string, but reservedWatts is entirely unexplained and units (watts) are only implied by parameter names.

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 tool performs a power-budget arithmetic comparison between a declared continuous allowance and device loads, which is a real purpose statement rather than a restatement of the name. However, it never says what the comparison produces (a verdict, a margin, a number) nor how the recorded BM24 mouse model relates to that arithmetic, so an agent cannot fully pin down the operation.

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?

It gives parameter-level hints ('use the seller's model field or exact variant name') but no when-to-use or when-not-to-use guidance, and no differentiation from the many sibling purchase tools. The trailing 'Check voltage, connectors, per-port limits and the setup guide' is advice-shaped but doesn't tell the agent which tool or condition selects this one.

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.