List all public FLOPS compute-price indices. Returns {count, indices[]} where each row is {index_id, family, value, unit, as_of, confidence, change_24h, delayed}. Use this to discover available indices before calling get_price or verify. No auth required.
| Name | Required | Description | Default |
|---|---|---|---|
| family_filter | No | Optional family prefix to filter by (e.g. 'FLOPS-H100' or 'FLOPS-B300'). Case-sensitive substring match. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the return format ({count, indices[]} with field names), the public nature of the data, and that no auth is required. It does not mention pagination or rate limits, but for this simple list-all tool, the disclosure is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main purpose and return structure. Every sentence provides value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite lacking an output schema, the description explicitly lists the return fields. It also provides usage context relative to sibling tools and notes authentication requirements. The tool is simple (one optional parameter), and the description fully covers its operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema fully documents the single parameter (family_filter) with clear semantics including case-sensitivity and substring match. The description adds no extra parameter details, but high schema coverage makes this acceptable per the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists all public FLOPS compute-price indices, includes the return structure, and differentiates from siblings by mentioning usage before get_price or verify. The verb 'List' and resource are specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says 'Use this to discover available indices before calling get_price or verify', providing a clear when-to-use directive. This also implies the alternatives (get_price, verify) for subsequent steps, meeting the explicit guidance criterion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct primary purpose: discovery (list/search), pricing (get_price), citation (get_index), and verification (verify). There is slight overlap between get_price and verify in 'current value' lookup mode, but descriptions clarify intended use cases.
Most tools follow a consistent verb_noun pattern in snake_case (get_index, get_price, list_indices, search_indices). The tool 'verify' deviates by using a bare verb without a noun, breaking the pattern slightly.
Five tools is well-scoped for a data lookup and verification server. Each tool covers a distinct need without bloat, and the count is within the ideal range for a focused service.
The tool set covers the full lifecycle for interacting with FLOPS indices: discover (list/search), retrieve current price (get_price), retrieve citation metadata (get_index), and validate values (verify). No obvious gaps for the stated purpose, as advanced features like source-level detail are intentionally excluded.