Skip to main content
Glama

modelread

modelread_mcp_list_hardware

List device presets: GPUs of every vendor, Apple Silicon, multi-GPU nodes, cloud instances (with $/hour), Jetson, phones, tablets, single-board computers and VPS tiers.

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

Input Schema

NameRequiredDescriptionDefault
limitNomaximum rows to return.
filterNowords matched against id / name / vendor / segment, e.g. "h100", "amd datacenter", "phone samsung".h100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully discloses that cloud instances include '$/hour' pricing and shows the breadth of the catalog, but it never confirms this is a read-only/safe operation, says nothing about pagination or ordering despite the limit parameter, and doesn't describe the shape of results.

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?

It is a single front-loaded sentence with no filler, starting with the verb and resource. The category enumeration is long but each term adds coverage 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 simple read-only listing tool with two fully documented optional parameters and no output schema, the description gives sufficient detail about what the catalog contains and even calls out pricing. It falls short only on pagination/results shape and safety, which the missing annotations leave unaddressed.

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 both limit and filter are already fully documented in the schema, including that filter matches against id/name/vendor/segment. The description adds little beyond implying the segments available, so the baseline 3 is appropriate.

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 uses a specific verb ('List') plus a specific resource ('device presets') and then enumerates the categories covered, so the agent knows exactly what comes back. It does not explicitly differentiate itself from siblings like modelread_mcp_compare_hardware or modelread_mcp_estimate_fit, but the catalog-listing intent is unambiguous.

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?

The intent to browse a hardware catalog is implied by 'List device presets', which is a reasonable when-to-use signal. However, there is no explicit guidance on when to use this versus the sibling compare/find/estimate tools, and no advice on when filtering is preferable.

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