Skip to main content
Glama

flop_inference_prices

Read-onlyIdempotent

Return every live FLOP inference model with the gateway's cost estimate for one request: cost_flop, input_tokens, output_tokens, gflops, latency_blocks. Needs no key and spends nothing. Use to compare miner inference costs before choosing a model for scout_answer, or to show the user what running a FLOP model costs at the network level.

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

Input Schema

NameRequiredDescriptionDefault
max_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds genuinely new operational facts: it needs no API key and spends nothing. It also discloses the response shape. It stops short of noting rate limits or whether the model list is cached/live-refreshed beyond the word 'live'.

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

Conciseness5/5

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

Two sentences, front-loaded with what is returned, followed by when to use it. No filler, no restatement of the name or title.

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?

With no output schema, listing the returned fields is the right call and is done well. The no-key/no-cost assurance covers the main pre-invocation question. The only hole is the undocumented max_tokens parameter and its effect on the estimate.

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

Parameters2/5

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

The single optional parameter max_tokens (32–800) has zero schema description coverage, and the description never mentions it. Given that the tool returns an output_tokens/cost estimate, an agent cannot tell whether max_tokens bounds the estimated output length and therefore changes cost_flop — a meaningful semantic gap.

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?

States a specific verb and resource ('Return every live FLOP inference model') and immediately enumerates the returned fields (cost_flop, input_tokens, output_tokens, gflops, latency_blocks), which cleanly separates it from siblings like flop_miner_ranking and scout_pricing. An agent can identify this as the cost-estimate enumerator without opening the schema.

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?

Gives concrete when-to-use guidance: compare miner inference costs before choosing a model for scout_answer, or surface network-level costs to the user. It names a sibling explicitly, but offers no exclusion against near-neighbors such as scout_pricing or scout_quote, so the agent must infer the boundary.

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.