Skip to main content
Glama
Sign In

SideQuest

by io.github.uckhill
OverviewDiscussionsAdmin

add_balance

Get a secure Stripe checkout link the person pays themselves to add prepaid balance (20 to 5000 USD), or buy a pack with bonus credit: starter (pay $100, get $110) or team (pay $250, get $280). Once paid, quests post and open instantly without a checkout step. Only the person can pay; you can't charge anything with this.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNoBuy a pack instead of a custom amount.
amount_usdNoHow much to add, in USD. Leave out when buying a pack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / amount_usd / description
      Previous value: -"How much to add, in USD."New value: +"How much to add, in USD. Leave out when buying a pack."
    • addedInput schema / properties / pack
      Added value: +{
+  "description": "Buy a pack instead of a custom amount.",
+  "enum": [
+    "starter",
+    "team"
+  ],
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "amount_usd"
-]
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the operation hands off to an external Stripe checkout, that the human — not the agent — must complete payment, the accepted amount range, and the post-payment effect on quest posting. These are the exact behavioral facts an agent needs before invoking a non-idempotent, open-world payment tool.

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?

Two sentences, front-loaded with the primary action and the return value, with the constraint last. The parenthetical pricing detail is dense but earns its place by conveying the pack bonus.

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?

With only two optional parameters and no output schema, the definition covers what is returned (a checkout link), the payment flow, and post-payment behavior. The one gap is that both parameters are optional in the schema, yet the description never states that exactly one of pack or amount_usd should be supplied.

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 coverage is 100%, so baseline is 3; the description goes further by spelling out the pack economics ($100→$110 starter, $250→$280 team) and restating the 20–5000 USD bound, which the enum alone does not convey. It stops short of stating that pack and amount_usd are mutually exclusive inputs.

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?

States a specific verb and result — obtaining a Stripe checkout link — plus the resource (prepaid balance) and the two modes (custom amount vs. bonus pack). The agent can immediately tell this is a payment-initiation tool, distinct from read-oriented siblings like get_balance.

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?

Gives clear context for use (adding balance so quests post and open without a checkout step) and an explicit exclusion: 'Only the person can pay; you can't charge anything with this.' It does not, however, name the sibling alternative get_balance or explain when to check balance instead of topping up.

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

All SideQuest 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