Skip to main content
Glama

modelread

modelread_mcp_find_models

Recommend open models for a task on a device, from a natural-language question. Ranks ~20k indexed Hugging Face models by fit, task benchmark percentile (vendor vs independent kept apart), quant quality and speed. Examples: "best coding model for an RTX 4090 + 64GB RAM at 32k context", "Japanese chat on a Galaxy S25 Ultra", "serve 8 users on 2x RTX 3090".

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

Input Schema

NameRequiredDescriptionDefault
questionNothe request in plain words; name the device in it, or set default_hardware.best coding model for an RTX 4090 with 64GB RAM at 32k context
default_hardwareNodevice used when the question names none (preset id, e.g. "m4max-128").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose useful context: it ranks roughly 20k indexed Hugging Face models and keeps vendor benchmark percentiles apart from independent ones. It does not state anything about the return shape (how many recommendations, with what scores), whether it is a pure read, or any latency/cost characteristics of the ranking.

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 compact sentences plus a short example list, with the purpose front-loaded and the ranking criteria immediately after. The examples are illustrative rather than padding, and no sentence restates the title or the name.

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 2-parameter tool with no annotations and no output schema, the description covers what it does and how to phrase input, but leaves the result shape unexplained (number of recommendations, presence of scores, pagination). An agent can call it, but cannot predict what it gets back.

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 parameters (question, default_hardware with the "m4max-128" preset example) are already documented in the schema. The description reinforces the device-in-question versus default_hardware fallback only implicitly through its examples and adds no syntax or format detail beyond the schema, so the baseline of 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?

States a specific verb and resource ("Recommend open models for a task on a device, from a natural-language question") and names the ranking signals (fit, benchmark percentile, quant quality, speed). The natural-language recommendation framing implicitly separates it from search/compare siblings, but no sibling is named explicitly, 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 Guidelines4/5

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

The three worked examples ("best coding model for an RTX 4090 + 64GB RAM at 32k context", "Japanese chat on a Galaxy S25 Ultra", "serve 8 users on 2x RTX 3090") make the intended usage concrete and tell an agent what a well-formed request looks like. There is no explicit when-not-to-use guidance or pointer to a sibling such as a plain keyword search or fit estimator.

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