Skip to main content
Glama

People pot

people_pot
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/arc/people/ ($0.002). Public People Pot summary. Does not pay anyone and does not look up one wallet. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses the paid x402 model, the $0.002 price, accepted rails (USDC on Arc/Base/Solana, XNT on X1), and that payment settles inside the tool call. That is exactly the kind of cost/auth context an agent needs before invoking. It does not cover failure modes (invalid or expired payment, whether a failed call is still billed), so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is dense but not wasteful in length; however it leads with a free-sample URL and price before stating the purpose, burying what the tool actually does. The price appears twice ("($0.002)" and "$0.002 per call"), which is a small redundancy.

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 one optional parameter, full schema coverage, and no output schema, the remaining risk is not knowing what the paid summary looks like; the free sample URL pragmatically covers that. The workflow, cost, and payment mechanics are all present, so an agent can invoke it correctly.

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 the baseline is 3, but the description adds real meaning: the parameter is optional on the first call (fetch terms) and, when supplied with a signed payload, completes the purchase in the same call. That sequencing is not evident from the schema's one-line property description.

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

Purpose3/5

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

"Public People Pot summary" implies a retrieval verb and resource, but "People Pot" is a product-specific term left undefined, so an agent cannot tell from the description alone what the returned summary contains. The negative scoping ("does not pay anyone and does not look up one wallet") does help distinguish it from a wallet-lookup or payout tool, which lifts it above a pure tautology.

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?

The description gives an explicit invocation protocol: call once without `payment` to receive terms, sign with your own wallet, then call again with `payment`. It also states what the tool is not for (no payouts, no single-wallet lookup), which implicitly routes the agent elsewhere.

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