Skip to main content
Glama
modelanalyzer-mcp

modelanalyzer-mcp

by yeaske

Search models

search_models
Read-only

Find AI models by name, ID, or maker and return IDs, pricing, cost per task, speed, context, and Analyzer Index for comparison and cost estimates.

Instructions

Find models by name, id or maker. Returns ids for the other tools, plus Analyzer Index, price, cost per task, speed and context.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesModel name, id or maker, e.g. 'claude sonnet' or 'gpt-6'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile and the open-world nature of the catalog search are covered. The description adds real value by enumerating the response fields including a ranking signal (Analyzer Index) and pricing metrics. It stops short of disclosing ordering, truncation, or what happens when no model matches, even though the 25-result cap implies a result ceiling.

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 short sentences, front-loaded with the action and matching fields before the return payload. The field enumeration in the second sentence is dense but functional. No filler or hedging.

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 correctly takes on the burden of stating what comes back, which it does at a field-family level. For a two-parameter, read-only search tool this is close to complete; the residual gaps are result ordering and limit behavior.

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 coverage is 50%: query is documented in the schema with examples, while limit has only numeric bounds and no prose. The description's "by name, id or maker" reinforces the query semantics but adds nothing the schema lacks, and it never explains what limit controls or how results are capped. With half the parameters documented only by constraints, this is the baseline rather than an improvement.

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 opens with a specific verb and resource ("Find models") and narrows the matchable fields to name, id or maker, which maps directly onto the query parameter. It also previews the payload (ids, Analyzer Index, price, cost per task, speed, context). It never names a sibling like compare_models or recommend_models, so the agent gets a clear purpose but no explicit differentiation.

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 phrase "Returns ids for the other tools" implies this is the lookup step that feeds downstream tools, which is a useful workflow hint. However, there is no explicit when-to-use versus when-not guidance, and nothing says how this differs from compare_models or recommend_models, both of which sound like plausible starting points for the same intent.

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