Pronto

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

Name	Required	Description	Default
`label`	No	A name for this agent, for whoever reviews the account later.
`public_key`	No	Base64-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.

AddedAug 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With annotations only indicating non-read-only, open-world, and non-idempotent, the description adds substantial behavioral detail: no human involvement, authentication via Authorization header, unauthenticated limits by default, claim-code flow, and credential expiration/rotation consequences. This goes well beyond the structured annotations.

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 longer than average but every paragraph adds necessary context: purpose, authentication, plan options, and key rotation. It is front-loaded with the core action and API key usage. Minor redundancy and dense phrasing keep it from a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description mentions the important response elements: the API key, claim code, and URL. It covers the identity lifecycle, plan implications, and rotation. It omits explicit error behavior and expiry duration, but the tool can be invoked correctly with the information provided.

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?

The input schema already covers parameter meanings, so the baseline is 3. The description adds valuable semantics for the public key parameter, explaining the base64 format, the private-half requirement, and the rotation implications, which exceeds what the schema alone communicates.

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 verb and outcome: create an identity and receive an API key. It clearly distinguishes this tool from the sibling billing and plan tools by focusing on registration and credential issuance.

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 explains when to use the tool (to create an identity) and what to do afterward, including alternatives for raising limits via get_plans/open_payment or a claim code. It does not explicitly state when not to use it, but the context is clear and routes the agent to relevant siblings.

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

All Pronto tools Inspect

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.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: get_signal re-reads a known row, get_latest_signals fetches by time, scope_signals filters by facets, search_signals matches words, and get_related_signals follows links. The overlapping pairs like get_facet_manifest/list_facets and get_fused_signal/list_fusion_products are explicitly differentiated in their descriptions, so an agent should not confuse them.

Naming Consistency5/5

The naming follows a consistent snake_case verb_noun pattern: get_ for direct fetches, list_ for catalog-style enumeration, register_ for identity creation, and scope_/search_ for query actions. The slight difference between get_fused_signal and list_fusion_products is meaningful and the verbs remain predictable.

Tool Count5/5

Thirteen tools is well within the sweet spot and each one covers a distinct capability: live reads, lookup by id, lexical search, facet filtering, related signals, fused products, catalogues, plans, billing, and agent registration. There is no obvious padding or excessive fragmentation.

Completeness5/5

The surface fully covers the domain: discovering the vocabulary, selecting signals, searching, fetching by id, following relationships, computing derived products, listing sources, and checking billing/plans. The only gaps would be account claiming and credential rotation, but those are explicitly deferred to external parties, so they are not tool-set gaps.

Resources

Need Help?