Skip to main content
Glama

pronto-stream

by io.github.nmxmxh

open_payment

Idempotent

Buy a plan 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.

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 plan 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 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
planYesThe plan to buy. Enterprise is a design partner engagement and cannot be bought here.
cycleNoBilling cycle. Defaults to monthly.
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. Dates show when Glama detected each change.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the binding side effect, why the wallet is bound before payment, the public-transaction-hash risk, and the oracle acceptance rule that only transfers from the named wallet settle. This is substantive behavioral context the annotations do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is well-structured and front-loaded with the core action, then prerequisites, then critical binding context, then return value and next step. The security rationale is relatively long but earns its place because it explains a non-obvious and consequential behavior.

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?

The description covers prerequisites, parameter semantics, side effects, return value, and the follow-up call. Even without an output schema, the agent knows exactly what comes back and what to do next. No critical gap remains for this tool.

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 description coverage is 100%, so the baseline is 3. The description adds real extra meaning for from_address: it explains why the wallet is bound now, what 'binding' means, and the settlement consequence. Plan and cycle are already fully described in the schema, so no more is needed.

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?

The description opens with a specific action—'Buy a plan for yourself'—and sharpens it into the actual step-one behavior: 'quotes the exact amount and binds the purchase to the wallet you will pay from.' This clearly distinguishes open_payment from settle_payment and get_plans.

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?

The description explicitly tells the agent to call register_agent first for identity, get_plans for plan details, and settle_payment after transferring. It also clarifies the self-serve nature by saying 'no human involved' and sets up the exact order of operations.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct operation: the two facet-listing tools are explicitly differentiated as quick manifest vs exhaustive listing, and search_signals vs scope_signals is cleanly split between lexical search and facet filtering. The billing/payment tools also form a clear lifecycle with no overlapping responsibilities.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern: get_* and list_* for reads, and action verbs like register_agent, open_payment, settle_payment, scope_signals, search_signals for operations. No mixed casing or inconsistent verb styles.

Tool Count5/5

15 tools is at the upper edge of the well-scoped range but each tool earns its place: five cover data retrieval, four cover discovery/metadata, and five cover identity/billing. No redundant or filler tools.

Completeness5/5

The surface covers the full workflow for the stated domain: discover vocabulary, search/scope the live wire, retrieve individual signals and related signals, compute fused products, register an identity, and purchase/activate a plan. The only apparent omissions, such as cancellation, are outside the described prepaid self-service flow.

Resources