Skip to main content
Glama
zhaoyue722

LLM Usage & Cost Tracker

recommend_provider

Recommends the cheapest LLM model fitting your token workload and budget, with optional provider and model filters.

Instructions

Recommend the cheapest priced model that fits the workload + budget.

v1 ranks by cost only. A future release will incorporate quality benchmarks (see quality_snapshot — the table is reserved for that purpose) and accept a quality_priority axis; for v1 those would rely on data we don't yet have, so the surface stays cost-only and honest.

expected_input_tokens / expected_output_tokens default to a nominal 1k/1k workload when absent; the reasoning notes when defaults are in use. budget_usd, when set, filters out models that exceed it — if nothing fits, falls back to the cheapest model overall (the result fields are required, so there's no "no match" return shape) and the reasoning says so plainly.

providers / models are optional whitelists (AND-combine when both passed). Both are applied before the budget cut, so an over- budget fallback returns the cheapest within the filter set rather than the cheapest priced model overall. A whitelist that matches nothing raises rather than fabricating a result — likely a spelling error in the caller's name list.

task_description is optional and echoed into the reasoning but does not drive selection — the tool isn't an LLM and can't interpret free text. Omit it (or pass None) and the reasoning opens with "Recommending …" instead of "For task 'X': …".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelsNo
providersNo
budget_usdNo
task_descriptionNo
expected_input_tokensNo
expected_output_tokensNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYes
providerYes
reasoningYes
alternativesYes
estimated_cost_usdYes
Behavior5/5

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

Without annotations, the description fully discloses behavioral traits: v1 cost-only, default token values, budget fallback, whitelist AND-combination, error on unmatched whitelist, and non-functional task_description. No contradictions.

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?

The description is longer but well-structured with clear sections. Every sentence adds value, though slight trimming could be possible. Front-loaded with the main purpose.

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

Completeness5/5

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

Given the tool's complexity (6 parameters, no required, no annotations), the description is extremely complete. It covers return reasoning, fallback behaviors, error cases, and future plans. The output schema exists but is not needed for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates by explaining each parameter's effect: models/providers as whitelists, budget_usd as filter with fallback, task_description as echoed only, and token defaults. Adds significant meaning beyond the schema.

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 clearly states the tool's purpose: 'Recommend the cheapest priced model that fits the workload + budget.' It uses a specific verb ('Recommend') and resource ('cheapest priced model'), and distinguishes from sibling tools like compare_providers and get_pricing.

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?

Provides detailed guidance on default behaviors, budget fallback, whitelist logic, and optional parameters. While it doesn't explicitly contrast with siblings, the context is clear enough for an agent to decide when to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhaoyue722/llm-usage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server