Skip to main content
Glama

agent-exec

One LLM chat completion with no account and no model key (paid, x402)

infer_chat

PAID: LLM chat completion for $0.0100, no account or model key: send messages, get {model, content, finish_reason, usage}. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply.

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

Input Schema

NameRequiredDescriptionDefault
modelNoThe tier to buy: fast. Omitted means fast.
messagesNo1..32 chat messages summing to at most 8000 chars, e.g. [{"role":"system","content":"You are terse. Answer in one sentence."},{"role":"user","content":"What is the capital of Japan?"}].
max_tokensNoCeiling on the answer, 1..2048. Omitted means 1024.
temperatureNoSampling temperature, 0..2. Omitted means 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and non-destructive; the description adds the substantial facts an agent needs beyond that: the tool is paid ($0.0100), requires no account or model key, will return a price quote when unpaid, and accepts payment on seven named chains. It also flags the out-of-band feedback endpoint and that feedback is read-only, which no annotation conveys.

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?

Pricing and the no-key benefit are front-loaded, then the response shape, then the payment mechanics, so the agent reads the most decision-relevant facts first. The trailing feedback sentence is marginally off-topic for invocation but is short and clearly separable.

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?

There is no output schema, yet the description enumerates the returned fields and explains both the unpaid (price) and paid (completion) response modes, which is exactly what's missing structurally. Combined with a fully described 4-parameter schema, an agent has everything needed to invoke it correctly.

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 model tier, message limits (1..32 messages, 8000 chars), max_tokens and temperature ranges are already fully documented in the schema. The description only repeats 'send messages' and adds no syntax or format meaning beyond that, so the baseline of 3 applies.

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 names a specific verb and resource ('LLM chat completion') plus price and the shape of the result ('{model, content, finish_reason, usage}'), and no sibling tool in the list does chat inference, so the tool is unambiguously identifiable.

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?

It gives the operative call sequence: call unpaid to get the price, then include the payment blob in _meta['x402/payment'] and call again. That is explicit procedural guidance with no competing alternative tool to route away from, though it doesn't cover failure/retry cases once payment is attached.

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.