Skip to main content
Glama

modelread

modelread_mcp_compare_hardware

Run one Hugging Face model against several devices and rank them (best first). Use for "which of my machines should run X" or "is a 4090 or an M4 Max better for X".

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_compare_hardware"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctxNocontext length in tokens (default 32768).
repoNoHugging Face repo id, e.g. "openai/gpt-oss-120b".openai/gpt-oss-120b
hardware_listNocomma-separated devices (preset ids or free text), up to 8.rtx5090, m4max-128, dgx-spark, h100-sxm

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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, and it leaves the costliest behaviors undisclosed: whether this actually executes the model (potentially a 120B default) or merely estimates, how long it takes, whether anything is downloaded, or whether ranking is by throughput, latency, or fit. Only the output ordering is revealed; the meaning of 'best' is undefined.

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, zero waste, with the operation and its ranking semantics front-loaded before the use-case examples. Nothing is redundant with the tool name or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter tool with full schema coverage, the description covers purpose and ranking order but omits the return shape and, critically, the cost/runtime profile of a multi-device run. With no output schema and no annotations, those omissions leave real uncertainty for an agent deciding whether to invoke it.

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%, with each of the three parameters (ctx, repo, hardware_list) documented including defaults and the 'up to 8' device cap. The description adds no parameter-level meaning beyond the schema, which is acceptable at full coverage but earns no extra credit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('compare/rank') and a precise resource ('one Hugging Face model against several devices'), and explicitly notes the output ordering ('best first'). This is clearly distinguishable from siblings like list_hardware or estimate_fit without opening any schema.

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

Usage Guidelines4/5

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

The two quoted example questions ('which of my machines should run X', 'is a 4090 or an M4 Max better for X') give a concrete, actionable fit for when to reach for this tool. It stops short of naming a complement such as a single-device estimate tool or stating exclusions, so it is clear context without explicit when-not guidance.

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