Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tollbooth_ledger

Tracks machine readers billed $0.01 USDC per link open via x402 on Base, returning paid-open counts, total USDC collected, and recent payer settlement transactions.

Instructions

[FREE] Live ledger of the TOLLBOOTH - the link that bills its readers. levelsio found thousands of bots open any posted link within 0.4s; this endpoint charges them $0.01 USDC per open via x402 on Base. Returns how many machine readers have paid, total USDC collected, and the recent payers with their on-chain settle txs. Human landing page: https://agentpaystore.com/tollbooth/ - the paid endpoint is https://agentpaystore.com/tollbooth/api/read ($0.01, HTTP 402 without X-Payment).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does cover the essentials: free access, no payment header required, read-only ledger contents, and the contrast with the paid endpoint that returns HTTP 402 without X-Payment. It omits rate limits, how many 'recent payers' are returned, whether totals are cumulative or windowed, and how frequently the ledger refreshes 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.

Conciseness3/5

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

The useful parts (free, what it returns, paid-endpoint contrast) are present but the levelsio/bot anecdote and the two full URLs pad a definition that could be two sentences. The key scoping fact — this endpoint is free — is front-loaded, which helps.

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 zero-parameter read tool with no annotations and no output schema, the description does the necessary work by naming the three return fields and disambiguating the free ledger from the paid read call. Remaining gaps (result size, freshness cadence) are modest for a tool this simple.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the empty schema is self-documenting. Baseline for a 0-parameter tool is 4.

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?

The description names a specific resource (the TOLLBOOTH ledger) and enumerates what it reports: number of paying machine readers, total USDC collected, and recent payers with settle txs. The concept is idiosyncratic but self-explanatory, and it explicitly separates this free ledger from the paid read endpoint. It does not differentiate itself from any sibling tool by name, which keeps it out of the top band.

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

Usage Guidelines3/5

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

The '[FREE]' marker plus the note that the paid endpoint is a different URL ($0.01, HTTP 402 without X-Payment) implies you call this one to inspect toll activity without spending. However, there is no explicit 'use this when… / do not use this when…' routing versus siblings like get_x402_market_heatmap or get_recent_settlements, so selection is left to inference.

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

Deploy Server

Other Tools