Skip to main content
Glama

Agent Exchange store

models_model

$0.002 via x402: One model in full: every price component (prompt, completion, cache read and write, web search, images, requests), context length, max completion tokens, modalities, supported parameters, knowledge cutoff, creation date. id= as on OpenRouter, e.g. anthropic/claude-sonnet-5.5. Pay 0.002 USDC through https://store.agentexchange.work/gw/models/model?id=anthropic/claude-sonnet-5.5 Via the Agent Exchan

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": {
      "id": "<id>"
    },
    "name": "models_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the $0.002 cost, the x402 payment mechanism, the USDC settlement, and that omitting payment returns the price instead of data. It stops short of describing failure modes, retry behavior, or what happens if the id is unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The return-field enumeration is front-loaded and useful, but the text is a single run-on sentence with a truncated tail ('Via the Agent Exchan') and redundant repetition of the price and the full payment URL. It is over-packed rather than tight.

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 must describe the return payload, and it does so thoroughly by listing the fields an agent will receive. The payment flow is also covered; only edge cases (invalid id, unpaid call semantics beyond the schema note) and the truncated final clause leave 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 genuine meaning beyond the bare 'id' property by specifying the id format ('as on OpenRouter') and giving a concrete example (anthropic/claude-sonnet-5.5). It also corroborates the x_payment behavior described in 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 verb and resource: retrieving one model's full specification, and enumerates exactly what is returned (price components, context length, max completion tokens, modalities, knowledge cutoff). It implicitly distinguishes itself from the list-oriented siblings (models_models, models_cheapest) via 'One model in full', though it never names them explicitly.

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 rather than stated: an agent can infer this is the single-model lookup and that the id must match OpenRouter convention. However, there is no explicit 'use this instead of models_models/models_cheapest when...' routing guidance, and the payment prerequisite is described mechanically rather than as a usage condition.

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