Skip to main content
Glama

readygpu: hardware for local AI

Compare two

compare_hardware
Read-onlyIdempotent

Two graphics cards or machines side by side in a market: memory, bandwidth, how many models each runs fully in memory, and the estimated speed of each on every model.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "compare_hardware"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst card or machine slug
bYesSecond card or machine slug
marketNoWhich market's catalogue: us, uk, de (Germany and the rest of the EU) or ca (Canada).us
contextNoContext length in tokens: 8192, 32768, 65536 or 131072.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Where to price it: us, uk, de (Germany and the rest of the EU) or ca (Canada)."New value: +"Which market's catalogue: us, uk, de (Germany and the rest of the EU) or ca (Canada)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description goes further by disclosing what the comparison actually yields: memory, bandwidth, the count of models that fit fully in memory at the given context, and estimated speed per model. It does not note that this is a computed estimate rather than a measurement, or whether missing slugs cause an error, which keeps it off a 5.

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?

A single front-loaded sentence listing the compared dimensions, with no filler. It is a sentence fragment with an implicit verb, but every clause (memory, bandwidth, model fit, speed) earns its place by pre-announcing a result field.

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?

With four fully documented parameters and no output schema, the description usefully previews what comes back, which is the main gap such a tool would otherwise have. Missing only edge-case behavior: unknown slugs, what happens when one card is absent from the selected market, and whether speed estimates vary by context length.

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 100%, so the schema already explains a, b, market and context including the enum values and the token-length options. The description only echoes 'in a market' without adding format, defaulting, or slug-resolution semantics, so the baseline 3 applies.

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?

The description states a specific resource and action: two graphics cards or machines compared side by side, and enumerates the compared dimensions (memory, bandwidth, models fitting in memory, estimated per-model speed). That is far better than a tautology. It stops short of naming how it differs from siblings like hardware_details or best_hardware, so an agent must infer the distinction from the two-slug requirement.

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?

Usage is only implied: the word 'Two' plus the requirement for two slugs signals a two-item comparison rather than a single lookup. There is no explicit when-to-use guidance, no exclusion of hardware_details (one item) or best_hardware (ranking), and no mention that both slugs must exist in the chosen market's catalogue.

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.

Resources