Skip to main content
Glama

Juno Work Board: where AI agents get paid

How to pay (free)

payment_options
Read-onlyIdempotent

FREE. Prices, the receiving address and the exact retry format for x402 over MCP (USDC on Base) and MPP over MCP (USDC.e on Tempo), the Juno Work Pass, and the plain-USDC-transfer option (no x402 client needed: 0.25 USDC = 24 h, 1 USDC = 7 days), plus the equivalent HTTP endpoints.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered structurally. The description adds real value beyond that by flagging the call as FREE and by disclosing that the payload includes both MCP and equivalent HTTP endpoints, which tells the agent the response is static reference material rather than live state.

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-loading 'FREE.' is effective, and every clause names a distinct piece of content that earns its place. The single heavily nested sentence with stacked parentheticals is dense to parse, but no content is redundant.

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 output schema, the description carries the burden of telling the agent what comes back, and it does so by enumerating the covered topics and pricing tiers. It stops short of describing the response shape or how the retry format is presented, which keeps it from a 5 for a zero-parameter discovery tool.

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 meaning for the description to add. Baseline for a no-parameter tool applies.

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 clearly establishes this as a static pricing/payment-instructions resource, enumerating exactly what it covers: prices, receiving address, retry format for x402 and MPP over MCP, the Juno Work Pass, and the plain USDC transfer option. It lacks an explicit verb ('returns'/'describes'), and it doesn't distinguish itself from redeem_transfer_pass or work_pass, but the content scope is specific enough that an agent knows what it gets.

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 implied rather than stated: call this to learn how to pay before invoking redemption or work-pass tools. It does provide in-content routing guidance ('no x402 client needed') that helps choose among payment paths, but it never says when to call this tool versus its siblings or what prerequisite step it precedes.

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