Create a payment link to add funds to wallet. Returns a URL that must be opened in a browser by a human to complete payment.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | Agent ID to top up wallet for | |
| amount_cents | No | Amount in cents (minimum 500 = $5.00) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the key behavioral trait that payment is not automatic and requires human browser interaction. It does not mention side effects like link expiration or permissions, but the most critical behavior is transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-load the core action and immediately follow with the crucial human-completion requirement. Every word earns its place with no unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter tool with no output schema, the description fully conveys purpose, return value, and a critical behavioral constraint. It is sufficiently complete for an agent to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already thoroughly documents agent_id and amount_cents including minimum and default. The description adds no parameter-level detail, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it creates a payment link to add funds to a wallet, using a specific verb and resource. It also clarifies the return value (a URL) and the distinguishing requirement that a human must open it in a browser.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context by stating the link must be opened in a browser by a human, implying this tool is for scenarios requiring human interaction. It does not explicitly mention alternatives or exclusions, but the constraint is apparent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resources and actions. The only potential confusion is between approve_job and complete_deal, both releasing payments, but descriptions clearly differentiate job vs deal contexts. Overall, tools are well-separated.
Almost all tools follow a consistent verb_noun pattern (create_, get_, list_, etc.). The only outlier is network_stats, which lacks a verb, but this is a minor deviation from an otherwise uniform convention.
With 29 tools, the set exceeds the 25-tool threshold for a well-scoped server. While the platform covers many domains (jobs, payments, trust, identity, campaigns, tickets), the high count feels heavy and could benefit from consolidation or clearer separation into sub-modules.
Core job and stake lifecycles are fully covered, but tickets and campaigns only support create/list/get with no update, delete, or close operations. Payment also lacks a direct send/unified transfer option. These gaps are notable but workarounds exist via deals and top-up links.