Skip to main content
Glama

pronto-stream

by io.github.nmxmxh

register_agent

Create your own identity on pronto and receive an API key, with no human present. Send the key back as an Authorization header on later calls and you will be recognised across sessions.

Registering grants no plan. A new identity has exactly the limits an unauthenticated caller has. There are two ways to raise them, and you can take either. If you hold your own funds, call get_plans and then open_payment — you buy your own plan and no person is involved at any point. If your costs belong to someone else, hand them the claim code and URL in this response; once they claim you, your calls resolve to their plan with no change on your side.

Supply an Ed25519 public key (base64) if you can keep the private half: it lets you rotate your own credential before it expires without anyone's help. Without one you cannot rotate, and you must register again when the key expires.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoA name for this agent, for whoever reviews the account later.
public_keyNoBase64-encoded Ed25519 public key, 32 bytes. Optional, but without it you cannot rotate your own credential.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this as non-read-only and non-idempotent; the description goes beyond them by disclosing that registration grants no plan, that limits match an unauthenticated caller, that the API key must be sent as an Authorization header, and the rotation/expiration consequence of omitting the Ed25519 public key. No annotation contradiction is present.

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 purpose is front-loaded and each paragraph covers a distinct concern: core identity/API key, plan/limit/billing options, and key-rotation tradeoffs. It is long but not bloated; slight repetition of the no-human theme costs it a perfect score.

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 names the response elements (API key, claim code, URL), explains the auth header mechanics, states default limits, and lays out both plan-raising paths. An agent has enough to invoke register_agent and know what to do with the result.

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 meaningful param context for the public key by explaining why it matters—credential rotation without help and the forced re-registration if omitted—giving agents deeper understanding beyond the raw schema text.

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 states a specific action and outcome: 'Create your own identity on pronto and receive an API key'. It is clearly distinct from the sibling get_/list_/payment tools, and the registration purpose is unambiguous.

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

Usage Guidelines4/5

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

It clarifies when to use this tool: when an identity/API key is needed without human involvement. It also provides post-registration branching guidance—get_plans/open_payment for self-funded plans, or sharing the claim code/URL for third-party coverage—and warns when re-registration is required, though it does not explicitly contrast register_agent with a direct alternative.

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