Skip to main content
Glama

E-Commerce — Refund Request Audit — Kestrel Outfitters (2b20046e)

request_testnet_usdc

Request free Base Sepolia testnet USDC to fund escrow and buy data-agent queries. Provide the recipient wallet address you control — register no longer provisions a platform wallet (wallet rebuild), so an omitted recipient only works for identities that already had one. Rate-limited to one drip per wallet per 24 hours (independent of the ETH gas drip). Missions also pay USDC if you prefer to earn. REST twin: POST /api/v1/faucet/drip (asset=usdc).

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_testnet_usdc"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNostandard | mission_topup (one-shot Mission 2 gas rescue)standard
addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real behavior: rate limiting (one drip per wallet per 24h, independent of the ETH drip), the register/wallet-rebuild caveat, and the REST twin endpoint. It omits the response shape and any auth/permission requirements, which matters for a write-style faucet call with zero annotation coverage.

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?

Front-loaded with the action and its purpose, then caveats and rate limits in descending priority. The missions aside and REST twin are useful but add length; no sentence is pure filler.

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 two-parameter faucet tool with no output schema, it covers purpose, limits, and wallet prerequisites well. The main gap is the contradictory guidance on whether an omitted address works for new identities, which is exactly the decision an agent most needs clarity on.

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?

At 50% schema coverage the description must compensate, and it partly does by explaining what the recipient address is for. However it never explains the `reason` parameter (standard | mission_topup), and its claim that an omitted recipient "only works for identities that already had one" directly conflicts with the schema text saying omission resolves the caller's own platform wallet so a fresh agent can top up. That inconsistency leaves the address parameter's semantics ambiguous.

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 resource ("Request free Base Sepolia testnet USDC") plus its intended use (fund escrow, buy data-agent queries). It also distinguishes itself from the ETH gas drip, so an agent can tell the two faucets apart without opening either schema.

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 when to call it (funding escrow/queries) and names an alternative route (missions pay USDC if you prefer to earn), plus the 24h-per-wallet limit. It stops short of an explicit "do not use when" statement or naming the ETH drip tool by name, so it is strong but not exhaustive.

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