Skip to main content
Glama

readygpu: hardware for local AI

Best hardware lists

best_hardware
Read-onlyIdempotent

The ranked 'best for local AI' lists of a market (all graphics cards, cards under a price, used cards, Macs and mini PCs): best first by the most capable model each runs fully in memory. Prices are on each list's page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "best_hardware"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoWhich list: us: gpus, gpus-under-300, gpus-under-500, gpus-under-1000, gpus-under-2000, used-gpus, machines; uk: gpus, gpus-under-300, gpus-under-500, gpus-under-1000, gpus-under-2000, used-gpus, machines; de: gpus, gpus-under-300, gpus-under-500, gpus-under-1000, gpus-under-2000, used-gpus, machines; ca: gpus, gpus-under-400, gpus-under-700, gpus-under-1400, gpus-under-2800, used-gpus, machines. Lists with too few priced entries are not published.gpus
marketNoWhich market's catalogue: us, uk, de (Germany and the rest of the EU) or ca (Canada).us

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 cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds meaningful context beyond them: the sort order (best first by largest fully-in-memory model), and the important caveat that prices live on each list's page rather than in the returned data. It does not describe entry shape or list size, which keeps it short of 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?

Two sentences, front-loaded with what is returned and followed by the ranking rule; the trailing note about prices on the list page is short and useful. The lead sentence is dense but nothing is redundant.

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 does the necessary work of explaining what comes back (an ordered list per market) and what does not (prices). For a 2-parameter, read-only tool with full schema coverage this is largely sufficient; only the shape of individual entries is left unstated.

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 the `list` parameter's enum-like description enumerates every valid value per market, so the schema already carries the parameter semantics. The description reinforces that a list belongs to a market but adds no format or selection guidance beyond what the schema states.

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?

It states a specific resource — the ranked 'best for local AI' hardware lists for a market — and defines the ranking rule ('best first by the most capable model each runs fully in memory'), which is enough to tell it apart from search-style siblings such as find_hardware. It never explicitly names those siblings, though, so differentiation is inferred rather than stated.

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 implied: call this when you want a pre-ranked catalogue of recommended hardware rather than a lookup. There is no explicit 'use this when' guidance, no exclusion, and no pointer to find_hardware, compare_hardware or hardware_details as the alternative for different needs.

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