Skip to main content
Glama

grid402_pass

Idempotent

x402 Prepaid Session Pass issuance (Starter 2 USDC = 400 credits, Pro 5 USDC = 1,000 credits, Fleet 20 USDC = 6,000 credits) or status check.

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

Input Schema

NameRequiredDescriptionDefault
statusNoOptional existing pass_g402_... token to check status without issuing a new pass.
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / status / description
      Added value: +"Optional existing pass_g402_... token to check status without issuing a new pass."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the write/idempotent profile is covered. The description adds useful pricing tiers and hints that supplying a token avoids a new issuance, but it omits critical behavior for a payment tool: that issuance requires a valid on-chain payment proof, what happens on failed payment, and whether a pass is returned and reusable.

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?

A single sentence front-loads the purpose before the parenthetical pricing detail, and nothing is redundant. The tier pricing inside parentheses is somewhat dense but is the tool's core commercial context rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should clarify what issuance and status checks return (e.g., a pass_g402_ token and credit balance). It also doesn't explain the payment prerequisites implied by the open-world, non-read-only annotations, leaving meaningful gaps for a payment-mutating tool.

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?

Schema description coverage is 100% and both parameters are well documented in the schema itself (status token, Base Mainnet txHash, EIP-3009 payload, demo mode). The description adds no parameter-level meaning beyond the pricing tiers, which don't map to either parameter, so the baseline 3 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 states the specific resource (x402 Prepaid Session Pass) and the two modes (issuance or status check), plus concrete tier pricing. It is clear what the tool does, though it never names or contrasts with sibling tools such as grid402_pass_balance, which also sounds pass-related.

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?

The schema's 'status' parameter implies the check-vs-issue branch ('without issuing a new pass'), but the description itself gives no explicit when-to-use guidance, no prerequisites, and no routing to alternatives for checking credits or balances.

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