Skip to main content
Glama

silex_session_pass

Idempotent

Check balance or mint a 0ms Prepaid Bearer Pass (spass_...) from a single Nano txHash so your agent unlocks hundreds of feeds in <8ms with zero per-call blockchain wait.

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": {
      "txHash": "<txHash>"
    },
    "name": "silex_session_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashYes64-character hexadecimal Nano ($XNO) mainnet send block hash funding the prepaid pass.
passTokenNoOptional existing Silex Prepaid Bearer Pass token (spass_...) to check remaining USD micro-balance or top up.
usdAmountNoOptional target USD deposit amount corresponding to the Nano transaction (e.g. 1.00).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / passToken / description
      Added value: +"Optional existing Silex Prepaid Bearer Pass token (spass_...) to check remaining USD micro-balance or top up."
    • addedInput schema / properties / txHash / description
      Added value: +"64-character hexadecimal Nano ($XNO) mainnet send block hash funding the prepaid pass."
    • addedInput schema / properties / usdAmount / description
      Added value: +"Optional target USD deposit amount corresponding to the Nano transaction (e.g. 1.00)."
  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, destructiveHint=false and openWorldHint=false, so the mutation/idempotency profile is covered structurally. The description adds real context beyond that — the pass is funded by an on-chain Nano send and removes per-call blockchain latency — but says nothing about what happens on an invalid or already-consumed txHash, confirmation requirements, or what value is returned.

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 structural waste, opening with the dual action and ending with the latency benefit. The '0ms'/'<8ms'/'hundreds of feeds' phrasing leans promotional, but it does not obscure the mechanic.

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?

With three fully documented parameters and annotations carrying the safety/idempotency profile, the definition is largely self-sufficient. The remaining gap is returns: there is no output schema, yet the description never indicates what an agent receives (remaining balance, or a minted spass_ token) on either the check or mint path.

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 the schema already explains txHash, passToken and usdAmount in detail, and the baseline is 3. The description only reinforces that a single txHash is the funding source and shows the spass_ token prefix, adding marginal meaning beyond the schema.

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 names specific verbs (check balance, mint) and a specific resource (Prepaid Bearer Pass), plus the exact input that drives it (a single Nano txHash). It is distinguishable from the sibling feed/query tools, though it never explicitly contrasts itself with any of them.

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 context is present but motivational rather than directive: 'so your agent unlocks hundreds of feeds in <8ms with zero per-call blockchain wait' tells the agent why to mint a pass, not when to call it instead of alternatives such as a direct feed tool. No exclusions, prerequisites, or alternative-routing guidance are given.

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.