Skip to main content
Glama

Journey mints

journey_mints
Read-onlyIdempotent

Free sample: https://apexfaucet.xyz/journey/ ($0.001). Recorded Journey badge mint count. A floor. Does not mint. $0.001 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": "journey_mints"
  }
}

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.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the $0.001 per-call cost, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and that the first unpaid call returns terms rather than data — all valuable context annotations cannot express. It does not say what happens on payment failure or whether repeat calls are billed again, which sits somewhat awkwardly with idempotentHint=true.

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 short and front-loads the free sample and price, but the $0.001 amount appears twice, and fragments like 'A floor.' and the bare URL interrupt the flow of an otherwise tight two-sentence structure.

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 one-parameter tool with no output schema, the description covers cost, payment mechanics, and the no-mint caveat, which is what an agent needs to call it correctly. It could go slightly further by describing the shape of the returned count, but the essentials are present.

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% and the single `payment` parameter is already documented as a base64 x402 payload. The description still adds meaning by explaining the two-step terms-then-payment flow and that passing the parameter completes the purchase inside the call, which the schema alone does not convey.

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 states a concrete resource: 'Recorded Journey badge mint count,' and explicitly disambiguates it from the tool name by saying 'Does not mint,' so an agent won't expect a minting action. The fragment 'A floor.' is cryptic and leaves the exact semantics of the returned number slightly ambiguous.

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 explicit procedural guidance: call once without `payment` to get terms, sign them with your own wallet, then call again with `payment`. That is clear when-to-use sequencing. It does not name any alternative tool or say when this counter is useful versus other on-chain data tools, so it stops short of full routing guidance.

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