Skip to main content
Glama
Sign In

BotsRated (beta)

by com.botsrated
OverviewDiscussionsAdmin

Export records (plan token)

evidence_export
Read-onlyIdempotent

Plan bearer token, never x402. Signed records already stored for the plan's hosts: receipt ids and verify links. Not a zip.

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

Input Schema

NameRequiredDescriptionDefault
hostNoSeller hostname or URL, e.g. blockrun.ai or https://blockrun.ai/api/v1/chat/completions
sinceNo
tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior4/5

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

The description adds useful behavior beyond the annotations: it specifies that authentication uses a plan bearer token, not x402, that records are already stored and signed for the plan's hosts, that the output includes receipt ids and verify links, and that it is not a zip archive. These details are consistent with the read-only, idempotent annotations and help an agent understand the operation's scope and output shape.

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 description is short and contains no obvious filler, but it is written as terse fragments rather than a coherent sentence. The front-loaded token constraint is useful, though the phrasing 'never x402' and 'Not a zip' requires interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read-only export tool with no output schema, the description covers authentication and the general return content, but it leaves the since parameter and the exact export scope underspecified. It is minimally adequate rather than fully complete.

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 only 33%, so the description must compensate. It adds meaning for the token parameter by requiring a plan bearer token and excluding x402, and it contextualizes host as the plan's hosts, but it does not explain the since parameter or how records are filtered by date.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description implies exporting signed receipt records and verify links for a plan's hosts, but it does not use a clear verb-and-resource statement like 'Export records'. It distinguishes the output from a zip and clarifies the token type, yet it does not differentiate the tool from siblings such as receipt_verify or history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance about when to use this tool versus alternatives. The instruction to use a plan bearer token and 'never x402' is an authentication constraint, not usage guidance for selecting this tool over other record-related tools.

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

All BotsRated (beta) toolsInspect
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