Skip to main content
Glama

List hardware classes

list_hardware_classes

Lists hardware classes with measured FPS tweak data, showing tweak and machine counts per class. Call it first to get a valid hardware class before using any other tool.

Instructions

Hardware classes that have measurements, with how many tweaks and machines each one covers. Call this first: every other tool needs a hardware class, and guessing the name will fail.

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": "list_hardware_classes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full load. It usefully discloses the return content (classes with tweak/machine counts) and the failure mode of guessed names, but says nothing about whether the list is exhaustive or filtered, whether counts are scoped, or how the data is ordered/paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the actionable instruction ('call this first') is front-loaded after the one-line purpose. Nothing could be removed without losing information.

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 trivial zero-parameter discovery tool this is close to sufficient: purpose, payload, ordering, and failure mode are all covered. The only gap is the exact shape of the returned list, which the absent output schema leaves to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning the description needs to supply. Baseline of 4 applies; nothing about the empty schema is left ambiguous.

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 the resource (hardware classes) and its scope (only classes that have measurements) plus the returned payload (tweak and machine counts per class). It does not explicitly contrast with list_tweaks, but 'call this first' implicitly positions it as the discovery entry point, which is enough to distinguish it from the sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit ordering guidance ('Call this first'), a dependency rule ('every other tool needs a hardware class'), and the consequence of skipping it ('guessing the name will fail'). That is precise when-to-use direction with a stated failure mode, which is more than most definitions offer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.