Skip to main content
Glama

create_session_deposit

Prepay 0.006 SOL or 0.85 Base USDC once to receive a session token valid for 10 instant scan, audit, simulation, or scraping calls with 0ms RPC latency.

Instructions

Prepay 0.006 SOL or 0.85 Base USDC once to receive a session_token good for 10 instant calls across scan_code, audit_token, simulate_tx, and scrape_url with 0ms RPC latency.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deposit_tx": "<deposit_tx>"
    },
    "name": "create_session_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
deposit_txYesSolana transaction signature (0.006 SOL) or Base transaction hash (0.85 USDC)
payer_walletNoOptional wallet address of the depositing agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose useful behavior: cost, one-time prepayment, the 10-call quota, and cross-tool scope. It omits critical mechanics for a payment tool - whether the token expires by time or by count only, whether a deposit is refundable, whether verification is atomic, and (most importantly for a follow-up call) how the session_token is passed to subsequent tools.

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 front-loaded sentence with no filler; every clause (price, quota, tool list, latency) carries information. It is dense to the point of being run-on, but nothing is wasted.

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?

No output schema exists, yet the description never explains what the returned session_token looks like or where to supply it, which is the single most important downstream fact for this tool. Payment terms and token drawdown rules are partially covered but expiry and failure modes are missing.

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 coverage is 100% and both parameters are already documented in the schema, including the dual-chain deposit formats. The description's pricing figures mirror the schema rather than adding new per-parameter meaning, so baseline 3 applies.

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

Purpose5/5

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

Specific verb ("Prepay") plus resource (deposit for a session_token), with concrete pricing, quota (10 calls), and the exact set of tools the token unlocks. An agent can tell this is the paid-entry tool in the family, distinct from the four sibling action tools it enables.

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 makes the payoff explicit ("10 instant calls ... with 0ms RPC latency"), which tells the agent when this is worth doing instead of paying per call. It stops short of any exclusion or prerequisite guidance - it never says what happens without a deposit, whether calls are still possible rate-limited, or when a deposit is unnecessary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.