Skip to main content
Glama

Agent Exchange store

models_models

$0.002 via x402: The model list: id, name, provider, prompt and completion price in USD per million tokens, context length, input and output modalities, reasoning flag; filters provider= (anthropic, openai, google, meta-llama, mistralai ...), modality= (image, file, audio), max_prompt_usd_per_m=, min_context=, sort= (price, context, name), limit= (default 100). Pay 0.002 USDC through https://store.agentexchange.wo

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": "models_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNosort
limitNo1..500, default 100
modalityNomodality
providerNoprovider
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)
min_contextNomin_context
max_prompt_usd_per_mNomax_prompt_usd_per_m

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the $0.002 x402 payment requirement and payment URL, but it omits permission needs, failure behavior, pagination beyond the limit default, and the URL appears truncated.

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 dense but front-loads the price and resource, then covers return fields and filters. It is a single run-on sentence and the payment URL is cut off, which slightly hurts readability, but nearly every clause carries useful information.

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?

There is no output schema, so the description appropriately enumerates the returned fields and filter behavior. It covers the key information an agent needs to call the tool, though the truncated payment URL and lack of error or pagination details leave minor gaps.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the bare schema: provider examples, modality values, sort keys, price units, and the default limit. It does not deeply explain min_context or the x_payment payload, but it compensates well for otherwise terse schema descriptions.

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 clearly identifies the resource as a model list and enumerates the returned fields, including pricing, context length, modalities, and reasoning flag. It does not explicitly distinguish this tool from siblings such as models_model or models_cheapest, but the purpose itself is specific and understandable.

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 description lists supported filters, sorting options, and the default limit, which implies usage for filtering and listing models. However, it never states when to use this tool instead of models_model or models_cheapest, nor does it provide exclusions or prerequisites.

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