Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

agent_session_open

[$1.00] Deposit $1.00 USDC once to mint an HMAC-signed Bearer session token (x402s_...) for zero-402 high-frequency API calls with atomic balance debits.

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

Input Schema

NameRequiredDescriptionDefault
ttl_minutesNoSession lifetime in minutes (default 60, max 1440)
payer_addressNoEVM wallet address opening the session (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses the $1.00 cost, one-time deposit, token prefix, signed-token nature, and atomic balance debits. It omits failure/refund behavior and token expiry semantics beyond what the schema provides for ttl_minutes.

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

Conciseness5/5

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

A single dense sentence with the cost and primary action front-loaded. Every clause contributes useful information without 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?

For a two-parameter session-minting tool with no output schema, the description explains the cost, resulting token, and intended high-frequency use. It is nearly complete, though it could clarify refund/failure behavior and the token's lifecycle.

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%, so ttl_minutes and payer_address are already documented. The description adds the $1.00 cost and one-time session concept but no additional meaning for either parameter.

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 uses specific verbs and resources: deposit $1.00 USDC once to mint an HMAC-signed Bearer session token. It is immediately clear what the tool does, though it does not explicitly distinguish itself from any sibling tool.

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 a clear usage context: open a session for zero-402 high-frequency API calls. It does not state when not to use it or name an alternative, but the intended scenario is evident.

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