Skip to main content
Glama

Agent Tollbooth 402

Pricing & Net Revenue Quote

tollbooth_pricing_quote
Read-onlyIdempotent

Compute clearinghouse fee and developer net payout across Free BYO x402 (0%), Hybrid (7%), and Tollbooth Pro/Agency (3%) tiers in integer USD microdollars.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "priceMicros": "<priceMicros>",
      "callsPerMonth": "<callsPerMonth>"
    },
    "name": "tollbooth_pricing_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceMicrosYesPer-call price in integer USD microdollars (1 USD = 1000000 microdollars, e.g., 10000 for $0.01).
callsPerMonthYesEstimated monthly paid API or MCP tool calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so safety is covered. The description adds the useful tier/rate table, but it never explains how the tier is determined — there is no tier parameter in the schema — leaving a behavioral gap about which rate the quote will use.

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?

A single dense sentence with no filler and the key rates front-loaded. It is efficient, though the compression leaves the tier-selection question unaddressed.

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?

Rated against a simple two-parameter read-only calculator: the description states what is computed, the tiers/rates used, the integer microdollar unit of account, and names the output values (fee and net payout). Given annotations cover the safety profile and the schema covers inputs, nothing essential is missing for correct invocation.

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 coverage is 100%, with both parameters fully documented including the microdollar unit convention, so the description adds essentially nothing beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 verb (compute) and specific outputs (clearinghouse fee and developer net payout), and lists the exact tiers and rates involved. It is clearly distinguishable from siblings like verify_x402 or wallet_balance, though it does not explicitly name them.

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?

Usage is only implied: an agent can infer this is a pre-charge quote/calculator, but the description never says when to call it versus issuing a receipt or creating a top-up checkout, nor does it state prerequisites or exclusions.

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.