Skip to main content
Glama

request_funding

Read-onlyIdempotent

Retrieve agent and merchant testnet addresses, official token address, and faucet instructions to fund wallets; it does not claim tokens or sign transactions.

Instructions

Return agent and merchant testnet addresses, official token address, and faucet instructions. This tool never claims tokens or signs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=true, idempotent=true, non-destructive), so the bar is lower. The description still adds genuine value by disclaiming side effects that the 'request_funding' name might imply — it explicitly states the tool neither claims tokens nor signs anything. It does not describe whether returned addresses are static or per-session, but the core behavioral expectation is clear.

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, zero waste, and the return contents are front-loaded before the negative clarification. Every clause carries information an agent needs.

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 no input schema, no output schema, and a zero-parameter interface, the description carries the burden of describing what comes back — and it does list the three return items (agent/merchant testnet addresses, token address, faucet instructions). It is a very simple tool, so this is close to sufficient; only the exact response format remains implicit.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on nonexistent inputs.

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 uses a specific verb ("Return") and enumerates three concrete resources: agent and merchant testnet addresses, official token address, and faucet instructions. This corrects the potentially misleading name 'request_funding' by making clear the tool only surfaces addresses and instructions rather than moving funds. It stops short of naming a sibling tool, but the clarification that it "never claims tokens or signs" implicitly separates it from pay/transfer_* operations.

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?

Usage is only implied: an agent learns it should call this to obtain testnet addresses and faucet instructions. The negative clause ("never claims tokens or signs") hints that token-claiming is handled elsewhere, but no alternative tool is named and there are no explicit preconditions or when-not-to-use statements.

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