Skip to main content
Glama

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.001 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

TableJSON 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.001 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. 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"
+]
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations, the description discloses critical behavioral traits: the purchase is bound to the from_address before payment, repeated purchases extend existing plans, nothing renews automatically, called credits do not expire, failed calls are not charged, and returns PAY lines with the atomic amount. The security rationale for binding is also explained. This is unusually transparent for a payment tool.

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?

The description is long, but each section earns its place: overview, product options, prerequisites, binding rationale, and next step. It is organized and front-loaded with the core purpose. Some sentences could be tightened, but the density is justified by the complexity of a two-step payment flow.

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?

With no output schema, the description still enumerates what the return value contains ('PAY lines with the atomic amount, the token, the network and the address to pay'). It also covers prerequisites, edge cases around plan renewal, invalid plan types, and the follow-up call. An agent has enough context to invoke open_payment correctly and proceed to settle_payment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds substantial meaning: it details the credits plan pricing ($0.001 per call, one credit per successful call, Builder's limits, no expiry), explains that cycle defaults to monthly and is ignored for credits, and clarifies that from_address is required and binding for security reasons. This goes well beyond the schema's field descriptions.

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?

Description opens with 'Buy access for yourself, with no human involved' and immediately scopes itself as 'step one of two' in a payment flow, naming the exact quote-and-bind behavior. It clearly distinguishes itself from the sibling settle_payment by describing the two-step sequence, so an agent can tell them apart.

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?

Provides explicit when-to-use context: prerequisites ('call register_agent first'), discovery ('call get_plans'), and the next step ('then call settle_payment'). It also rules out enterprise plans ('cannot be bought here') and explains what is not covered, leaving no ambiguity about when this tool is appropriate.

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