Skip to main content
Glama
Sign In

Wazza

by ai.wazza
OverviewDiscussionsAdmin

Create a top-up link

create_topup_link

Makes a payment link for a credit pack. Give the link to a person: they pay on the payment page, and the credits land when the payment succeeds. The link expires after 24 hours.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pack": "<pack>"
    },
    "name": "create_topup_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
packYesThe credit pack.
promo_codeNoA promotion code, if the person has one. The price stays the pack's; the code adds bonus credits when the payment succeeds.
idempotency_keyNoOptional. Retrying with the same key and the same request within 24 hours returns the first answer instead of doing it twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-idempotent operation, so the bar is lower. The description still adds real value beyond them: the link's 24-hour expiry, the fact that credits are only delivered after successful payment, and the external payment-page flow that justifies openWorldHint. It does not warn about failure or partial states, but the key lifecycle facts are disclosed.

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?

Three short sentences, front-loaded with what the tool produces, followed by the lifecycle and expiry. No filler and no repetition of the title.

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?

For a three-parameter creation tool with no output schema, the description covers what is produced and how it behaves. The return shape (presumably a URL) is only implied by 'give the link to a person', and error behavior is unaddressed, which are the remaining small gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter carries its own description, so the schema does the heavy lifting. The description mentions the credit pack only implicitly through 'for a credit pack' and says nothing about promo_code or idempotency_key, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: 'Makes a payment link for a credit pack.' That is clearly distinct from the read-only siblings (get_balance, list_models) and the run-oriented ones. It does not explicitly name a sibling it substitutes for, but the 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 Guidelines3/5

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

'Give the link to a person: they pay on the payment page' does imply the use case and the audience, which is genuine context. However, there is no exclusion or alternative path (e.g. when to use this versus start_run or get_balance for credit handling), so the agent must infer the boundaries.

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

All Wazza toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources