Skip to main content
Glama

Reported AI Revenue Tracker export (paid, x402)

export_dataset
Read-onlyIdempotent

Returns the Reported AI Revenue Tracker in one call: AI businesses whose figures all come from press coverage, company announcements or filings (reported, not payment-verified), every figure with its as-of date and source_url, plus dated readings. format "csv" ($0.25 USDC via x402) or "jsonl" ($0.50); optional slug = one business, same price. Unpaid call = free preview + exact terms; nothing is charged without a signed payment. Free 10-row preview: https://mrrledger.com/data/reported/?ref=mcptool

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

Input Schema

NameRequiredDescriptionDefault
slugNoOptional: one business slug (tracker businesses only)
formatNocsv

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses the paid x402 flow, exact per-format prices, that an unpaid call returns a free preview plus terms, and that nothing is charged without a signed payment. It also describes returned fields (as-of date, source_url, dated readings), which is valuable given there is no output schema.

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?

Dense but front-loaded: what it returns first, then format/price, then payment terms, then the free preview link. The heavy parentheticals and price/URL detail make it slightly sprawling, but nearly every clause carries decision-relevant information.

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?

For a two-param paid export with no output schema and no required fields, the description covers provenance, return contents, pricing, payment safety, and a way to inspect data for free before paying. An agent has everything needed to call it correctly and warn a user about cost.

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 50% — slug is documented in the schema, format is only an enum plus default. The description compensates by giving per-format pricing ($0.25 csv, $0.50 jsonl) and clarifying that slug means one business at the same price, which the schema does not convey.

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 and resource: returns the Reported AI Revenue Tracker dataset in one call, with explicit scope (reported, not payment-verified figures). The 'reported vs payment-verified' framing distinguishes it from a presumably separate verified dataset, though no sibling tool name is cited to anchor that contrast.

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?

Clear usage context: pick csv or jsonl, optionally scope to one business via slug at the same price, and make an unpaid call for a free preview with exact terms. It does not, however, say when to reach for this export instead of siblings like get_business, search_businesses or compare_businesses.

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.

Resources