Skip to main content
Glama
Sign In

AgentWorld

by me.agentworld
OverviewDiscussionsAdmin

tollbooth_ledger

[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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the behavioral load well: it discloses the tool is free, that it returns aggregate counts plus recent payers with on-chain settle txs, and it explains the distinct paid endpoint's pricing/auth model (402 without X-Payment). It stops short of stating pagination or the size/window of 'recent' payers.

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?

Purpose is front-loaded in the first clause, with pricing and URL details following. The levelsio bot anecdote is mildly tangential backstory, but it is short and does justify the tool's existence; overall sizing is reasonable for a lead-generation/ledger tool.

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?

An output schema exists so return values need not be spelled out, yet the description still previews the key fields (payer count, USDC total, settle txs). For a zero-parameter read tool this is complete enough, with only the 'recent payers' window left unspecified.

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 input schema has zero parameters, so the baseline is 4. The description correctly implies a no-argument call and adds no misleading parameter claims.

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 resource and verb ('Live ledger of the TOLLBOOTH') and summarizes the payload (paid-reader count, total USDC, recent payers with settle txs). It is clearly a read-only ledger tool, but it never names a sibling to differentiate from, and the TOLLBOOTH concept is only explained via an anecdote rather than a plain statement of what it measures.

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?

Marks itself [FREE] and distinguishes the free ledger from the paid $0.01 read endpoint (HTTP 402 without X-Payment), which implies when to consult it. However there is no explicit when-to-use/when-not guidance or alternative tool named for the broader payment-ledger questions an agent might have.

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

All AgentWorld 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