Skip to main content
Glama

Recommend an LLM Model

recommend-llm-model
Read-only

Pick a model. Returns a ranked top 3 for one workload under optional constraints, each with a per-constraint satisfied/violated breakdown as the evidence. Use this when the user wants an ANSWER rather than a table — 'what should I use for support tickets under $500 a month'. To browse or filter the whole catalogue instead, use compare-llm-models. Constraints: (monthly budget, minimum ELO, required capability, self-hostability). Returns a top 3 as structured facts — efficiency rank, ELO, list and optimized cost, FinOps flag, volatility, and a per-constraint satisfied/violated breakdown. When nothing satisfies every constraint the query is reported as over-constrained, recommendations is empty, and the nearest misses are returned in nearMisses instead, each carrying the constraint it failed and flagged as a miss in the text. The ranking is computed server-side and is final.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minEloNoMinimum Chatbot Arena ELO score. Typical range 1000-1500; ~1400 is roughly frontier-class. Models with no ELO score never satisfy this.
opennessNoRequire a self-hostability bucket, derived from the licence: Open source, Open weights, Proprietary, Unknown
volumePresetNoMonthly request volume: 10k, 100k, or 1m. Default: 100k
useCasePresetYesWorkload shape, which sets tokens per request: supportTicket (1.5k in / 500 out), knowledgeQA (2k / 800), meetingSummary (10k / 1.2k, batch-eligible), marketingContent (2.5k / 1.8k), codingTask (3k / 2k), invoiceProcessing (1.5k / 600, batch-eligible), callSummary (2k / 700, batch-eligible), agentWorkflow (6k / 3k).
maxMonthlyBudgetNoMaximum monthly budget in USD at the given volume. Tested against the LIST-price monthly cost, not the caching/batch-optimized cost.
requiredCapabilityNoCapability the model must have: Text, Vision, Reasoning, Agents, Image Gen, Audio. There is no Code capability: for coding, pass useCasePreset codingTask.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
sourceYes
volumeYes
eloAsOfYes
dataAsOfNo
nearMissesYes
provenanceNo
catalogSizeYes
rankedCountYes
volumeLabelYes
useCaseLabelYes
candidateCountYes
overConstrainedYes
recommendationsYes
roiCalculatorUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / requiredCapability / description
      Previous value: -"Capability the model must have: Text, Vision, Code, Reasoning, Agents, Image Gen, Audio"New value: +"Capability the model must have: Text, Vision, Reasoning, Agents, Image Gen, Audio. There is no Code capability: for coding, pass useCasePreset codingTask."
  2. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.