Skip to main content
Glama
Sign In

pronto-stream

by io.github.nmxmxh
OverviewDiscussionsAdmin

open_payment

Idempotent

Buy access for yourself, with no human involved. Step one of two: this quotes the exact amount and binds the purchase to the wallet you will pay from.

Three things can be bought. Call credits: plan "credits" with amount_usd from 1 to 100, at $0.0001 a call — one credit per successful tool call, Builder's limits while the balance lasts, no expiry, failed calls not charged. A pass: plan "builder" or "team" with cycle "day" or "week". A plan period: the same plans with cycle "monthly" or "yearly". Nothing renews automatically; buying the same plan again before it ends extends it.

You must already have an identity — call register_agent first and send the key as an Authorization header. Call get_plans for the ladder and what each option raises.

from_address is required and is the wallet the USDC will leave. It is bound now, before the payment exists, because a transaction hash is public the moment it is mined: without the binding, anyone watching the settlement address could take your transfer and redeem it as their own. Only a transfer from the wallet you name here, redeemed with a signature from that same wallet, will settle this purchase.

Returns PAY lines with the atomic amount, the token, the network and the address to pay. Transfer it, then call settle_payment with the transaction hash.

Input Schema

NameRequiredDescriptionDefault
planYesWhat to buy: call credits, or a plan. Enterprise is a design partner engagement and cannot be bought here.
cycleNoPeriod for a plan. Defaults to monthly. Ignored for credits.
amount_usdNoWhole dollars of credits to buy, at $0.0001 a call. Required when plan is credits.
from_addressYesThe EVM address the USDC will be sent from, 0x followed by 40 hex characters. Binding, and required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / amount_usd / description
      Previous value: -"Whole dollars of credits to buy, at $0.001 a call. Required when plan is credits."New value: +"Whole dollars of credits to buy, at $0.0001 a call. Required when plan is credits."
  2. Changed5 schema fields changed
    • addedInput schema / properties / amount_usd
      Added value: +{
+  "description": "Whole dollars of credits to buy, at $0.001 a call. Required when plan is credits.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / cycle / description
      Previous value: -"Billing cycle. Defaults to monthly."New value: +"Period for a plan. Defaults to monthly. Ignored for credits."
    • changedInput schema / properties / cycle / enum
      Previous value: -[
-  "monthly",
-  "yearly"
-]New value: +[
+  "day",
+  "week",
+  "monthly",
+  "yearly"
+]
    • changedInput schema / properties / plan / description
      Previous value: -"The plan to buy. Enterprise is a design partner engagement and cannot be bought here."New value: +"What to buy: call credits, or a plan. Enterprise is a design partner engagement and cannot be bought here."
    • changedInput schema / properties / plan / enum
      Previous value: -[
-  "builder",
-  "team"
-]New value: +[
+  "credits",
+  "builder",
+  "team"
+]
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly=false, openWorld=true, idempotent=true; the description adds far more: no automatic renewal, re-purchase extends the existing period, failed calls are not charged, credits have no expiry, and the security rationale for binding from_address before the payment exists. The return shape (PAY lines with atomic amount, token, network, address) is also disclosed.

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?

Front-loaded with the two-sentence essence, then structured paragraphs for purchase options, prerequisites, and the binding rationale. Dense with useful information, but slightly verbose with mild redundancy between 'You must already have an identity' and 'from_address is required and is...'.

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?

No output schema exists, yet the description fully specifies the returned PAY lines and the required follow-up call, plus prerequisites, purchase matrix, and renewal semantics. Nothing an agent needs to invoke this correctly is missing.

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 100%, so the baseline is 3, but the description adds genuine meaning: from_address is 'the wallet the USDC will leave' and is bound at quote time for anti-front-running, and the plan/cycle mapping to credits vs pass vs plan period is explained in prose. It stops short of restating enum values in detail, which the schema already handles.

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

Purpose5/5

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

States a specific verb and resource: this quotes the exact amount and binds the purchase to the paying wallet, explicitly framed as 'step one of two' before settle_payment. An agent can distinguish it from settle_payment and get_plans without opening any schema.

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

Usage Guidelines5/5

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

Names prerequisites (call register_agent first, send key as Authorization header), points to get_plans for pricing, enumerates exactly which plan/cycle combinations are purchasable, and closes with the explicit next step: 'Transfer it, then call settle_payment with the transaction hash.' Exclusions are stated (Enterprise cannot be bought here).

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

All pronto-stream toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources