AgentIndex — measured reliability for agent services

bulk_export

Cursor-paginated bulk snapshot of endpoints or resources. PRICED: $0.25 in USDC on base via x402 -- no account, no API key, no invoice. Call without payment to receive the exact payment requirements, then call again with payment to be served. Returns a 1000-record page. Price is per page, not per record. Pass the returned cursor to continue.

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

Input Schema

Name	Required	Description
`type`	No	endpoints or resources (default endpoints)
`cursor`	No	Opaque cursor from the previous page
`payment`	No	Optional. An x402 X-PAYMENT header value. Omit it to receive the payment requirements for this call; supply it to be served. Price: $0.25
`protocol`	No	Filter by protocol

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / payment / description

Previous value: -"Optional. An x402 X-PAYMENT header value. Omit it to receive the payment requirements for this call; supply it to be served. Price: $2.00"New value: +"Optional. An x402 X-PAYMENT header value. Omit it to receive the payment requirements for this call; supply it to be served. Price: $0.25"

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / payment / description

Previous value: -"Optional. An x402 X-PAYMENT header value. Omit it to receive the payment requirements for this call; supply it to be served. Price: $0.50"New value: +"Optional. An x402 X-PAYMENT header value. Omit it to receive the payment requirements for this call; supply it to be served. Price: $2.00"

Changed1 schema field changedAug 22, 2026

changedInput schema / properties / payment / description

Previous value: -"Optional. An x402 X-PAYMENT header value. Omit it to receive the payment requirements for this call; supply it to be served. Price: $1"New value: +"Optional. An x402 X-PAYMENT header value. Omit it to receive the payment requirements for this call; supply it to be served. Price: $0.50"

AddedAug 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

No annotations exist, so the description carries the full burden and does so well: it discloses the cost ($0.25 USDC on base via x402), that no account/API key/invoice is needed, the page size (1000 records), that billing is per page not per record, and that the cursor must be passed to continue.

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?

Five short sentences, each earning its place, with the core purpose and the payment protocol front-loaded before pagination details. No filler.

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?

For a 4-param, no-annotation, no-output-schema tool, this covers pricing, auth posture, page size, and pagination adequately. It doesn't explain the `type`/`protocol` filter semantics, but those are documented in the schema.

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 real meaning beyond the schema: it explains the payment field's two-mode contract (omit vs supply) and clarifies the per-page billing semantics of `cursor` continuation, which the schema does not state.

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?

States a specific verb+resource: 'Cursor-paginated bulk snapshot of endpoints or resources.' An agent can tell this is a bulk-dump tool rather than a scoring or lookup tool, though it doesn't explicitly name which sibling it supersedes (bulk_score, get_rankings).

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 an explicit two-step invocation recipe: call without `payment` to get requirements, call again with `payment` to be served. Clear operational context, but no guidance on when this tool is preferable to sibling alternatives like bulk_score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentIndex — measured reliability for agent services tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?