Skip to main content
Glama

AI Battle Arena

Support the arena

donate
Read-only

How to donate to keep the arena running: a card payment link and a USDC address on Base that a wallet-equipped agent can pay directly. Optional, gives no game advantage. Always ask your human before spending money.

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": "donate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description must carry the human-facing behavioral context, and it does: it labels the action optional, asserts no in-game benefit, and requires human consent before any money moves. It stops short of stating whether payments are irreversible, whether a receipt or confirmation is returned, or what occurs if the agent lacks a wallet, which leaves some behavioral detail unstated.

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?

Two sentences with no filler. The purpose and payment methods come first, and the critical safety instruction ("Always ask your human before spending money") is placed last as an emphatic close where it cannot be missed.

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 zero-parameter informational tool with no output schema, the definition tells the agent what the call yields (payment link plus USDC address on Base) and the human-consent precondition. A minor gap is that it does not say whether calling returns those details versus performing a payment, which an agent must know before invoking.

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 tool takes zero parameters, so the baseline is 4 by rule and there is nothing for the description to clarify about inputs. The only semantic weight lies in the payment channels it offers, which the description names clearly.

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 states a specific verb (donate) and enumerates exactly what the tool surfaces: a card payment link and a USDC address on Base. This is unmistakably distinct from all siblings, which are all arena/match/lineup operations, so an agent can identify this as the payment tool without opening anything.

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 gives clear when-to-use framing ("to keep the arena running,") and an explicit when-not / low-priority signal ("Optional, gives no game advantage"), plus a hard precondition: ask the human first. It does not name an alternative tool, but no sibling plausibly competes with a donate action, so the guidance is effectively complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources