Skip to main content
Glama

readygpu: hardware for local AI

Hardware to run a model

hardware_for_model
Read-onlyIdempotent

For one model: how much memory it needs at each context length, and the fastest hardware (and the fastest Mac) that runs it fully in memory in a market, with their speeds. Links the model's page, which shows the cheapest and best-value picks with 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": {
      "model": "<model>"
    },
    "name": "hardware_for_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesA model slug, from search_models
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.6/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent, closed-world read, so the bar is low. The description still adds real content: it discloses the shape of the answer (memory per context length, fastest hardware, fastest Mac, speeds) and that the model page carries cheapest and best-value picks with prices.

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?

Two sentences with no filler and a front-loaded scope, but the first sentence is a tangled clause stack ('the fastest hardware (and the fastest Mac) that runs it fully in memory in a market') and 'Links the model's page' is an awkward verb. It is dense rather than wasteful, and could be restructured for faster scanning.

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 no output schema, the description carries the burden of describing returns, and it does so reasonably: memory needs across context lengths, fastest hardware and Mac, speeds, and the linked model page with prices. Minor gaps remain around units and whether 'fully in memory' is a hard filter.

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 coverage is 100%, so the schema already documents all three parameters including enum values and defaults. The description only echoes that a market and context length are involved, adding no syntax or selection guidance beyond the schema, 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 names a specific verb-and-resource combination: per-model memory requirements at each context length plus the fastest hardware and fastest Mac that run it fully in memory, with speeds. The phrase 'For one model' scopes it against the broader hardware siblings, but it never names best_hardware, find_hardware or compare_hardware explicitly.

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 by 'For one model' and the requirement of a model slug from search_models. Nothing states when to pick this over best_hardware or find_hardware, and no exclusions or prerequisites are given beyond the slug source.

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