Skip to main content
Glama

pronto-stream

by io.github.nmxmxh

get_billing_profile

Read-onlyIdempotent

Report who you are resolved as and what your plan grants: the agent identity behind this call, the funded account it acts for, the plan, the per-minute call ceiling, the per-response row budget, and which indicator set you may compute. Returns a CWF BILL line, a CREDIT line when a metering balance exists, and a NOTE line naming your state and its remedy when you are not entitled — unauthenticated, or registered but not yet claimed by a funded account. If unauthenticated, call register_agent next: it creates an identity with no human present. From there you can either buy your own plan with open_payment, or hand the claim code it returns to whoever holds your budget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description reveals conditional output behavior beyond the annotations: it returns a CWF BILL line, a CREDIT line only when a metering balance exists, and a NOTE line when not entitled. It also explains the unauthenticated state and its remedy, which is valuable context beyond readOnlyHint and idempotentHint.

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 front-loaded with the core reporting purpose, then adds conditional return behavior and routing guidance. Every sentence adds necessary context, and no filler or redundant restatement of the tool name or annotations is present.

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?

Given no parameters, no output schema, and rich behavioral nuance, the description covers the essential call context: what will be returned, under what conditions, what the different states mean, and what to do next. An agent has enough information to correctly invoke and interpret 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?

The input schema is empty, so there are no parameter semantics to document. With zero parameters, the baseline is 4, and the description correctly focuses on behavior rather than nonexistent input details.

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 names a specific action ('Report') and a specific resource ('who you are resolved as and what your plan grants'), then enumerates exactly what is reported: identity, funded account, plan, call ceiling, row budget, and indicator set. This clearly distinguishes the tool from siblings like get_plans or register_agent.

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 what to do when unauthenticated ('call register_agent next') and then presents the two follow-on paths: buy a plan with open_payment or hand the claim code to the budget holder. It also explains the conditions under which a NOTE line appears, giving clear context for when this tool is useful versus alternatives.

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