Skip to main content
Glama

readygpu: hardware for local AI

Hardware details

hardware_details
Read-onlyIdempotent

One graphics card or machine in a market: its specifications, which models it runs fully in memory at a context length and how fast, and a link to its page and prices.

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": {
      "slug": "<slug>"
    },
    "name": "hardware_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesA card or machine slug, from find_hardware
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 safety is covered. The description adds substantive value beyond that by disclosing the shape of the answer (specs, per-model memory fit at a context length, speed, price link), which annotations cannot convey and which matters since there is no output schema.

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 sentence that front-loads the resource and then lists return contents in priority order. It is dense but every clause conveys real information; a slight split into purpose/return would improve scanability.

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?

For a read-only, fully-specified 3-parameter lookup with no output schema, the description covers what the tool returns and how market/context affect the answer. Missing only explicit routing to sibling tools and any note on error behavior for unknown slugs.

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% and all three parameters are documented there, including the slug source and the market/context enums, so the baseline is 3. The description reinforces that results are market-scoped and context-length-dependent, but adds no syntax or format detail beyond the schema.

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?

States a specific resource (one graphics card or machine in a market) and enumerates the returned content: specifications, which models it runs fully in memory at a given context length and how fast, plus page link and prices. It is clearly a detail-lookup tool, though it never names the sibling (find_hardware/compare_hardware) it contrasts with.

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 description frames it as fetching one item from a market catalogue, which suggests it follows a lookup, but there is no explicit when-to-use guidance or exclusion relative to compare_hardware, best_hardware, or hardware_for_model. The slug provenance hint lives in the schema, not the description.

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