Skip to main content
Glama
modelanalyzer-mcp

modelanalyzer-mcp

by yeaske

Recommend models for a use case

recommend_models
Read-only

Recommends AI models for a given scenario by ranking benchmark quality against monthly cost, with optional budget and open-weights filters.

Instructions

AI Model Analyzer's current ranking for a use-case scenario, blending benchmark quality with cost at a typical workload. Optionally filter by a monthly budget at that workload or by open weights.

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": {
      "scenario": "<scenario>"
    },
    "name": "recommend_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 5)
scenarioYesScenario id or name from list_scenarios, e.g. coding-assistant
openWeightsOnlyNoOnly models with downloadable weights
maxMonthlyCostUSDNoOnly models at or under this monthly cost at the scenario's workload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so safety is covered. The description adds real value beyond them by disclosing the ranking methodology (quality blended with cost at a typical workload), which tells the agent why the ordering looks the way it does. It does not mention result shape or whether the ranking is cached/current in any stronger sense.

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 tight clauses with no wasted words, and the core output is stated first. The structure is a noun phrase rather than an imperative sentence, which is slightly less immediately scannable but still front-loaded.

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?

There is no output schema, so the description should hint at what comes back; it implies a ranked model list but does not characterize the fields or whether 'limit' default of 5 is noted (it is only in the schema). For a four-parameter read tool this is adequate, but a sentence on the returned ranking structure would close the gap.

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 the schema already documents all four parameters, making 3 the baseline. The description reinforces the two optional filters (monthly budget, open weights) and adds the 'at that workload' nuance tying cost to the scenario. It adds little syntax or format detail beyond the schema.

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 states a specific resource and result: a ranking of models for a use-case scenario, blending benchmark quality with cost at a typical workload. That is distinguishable from search_models and compare_models by the ranking-oriented output. It lacks an explicit verb ('Returns...'), which keeps it just short of a 5.

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?

Usage is implied by the optional filters: use it when you have a budget ceiling or an open-weights constraint. It usefully points at list_scenarios for obtaining a scenario id. It never says when to prefer this over compare_models or search_models, and gives no exclusion conditions.

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