Skip to main content
Glama

silex_unlock_with_tx_hash

Submit a 64-char hex Nano (XNO) mainnet send block hash in the X-Payment header to unlock a Silex URL for a single drop, cross-domain synthesis, 24h JSONL stream, or Whole-Keyword Pack.

Instructions

Submit a 64-character hexadecimal Nano (XNO) mainnet send block hash in the X-Payment header to unlock any single drop, cross-domain synthesis, 24h JSONL stream, or Whole-Keyword Pack.

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

Input Schema

NameRequiredDescriptionDefault
urlYesTarget With Silex URL to unlock
txHashYes64-char hex Nano mainnet send block hash

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the X-Payment header mechanism and the mainnet/64-char constraint, but says nothing about idempotency (can the same hash be replayed?), whether the unlock is permanent or single-use, what happens if the hash is invalid or already consumed, or what a successful response returns. For a payment-gated mutation tool this is a significant disclosure gap.

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 dense sentence with the action front-loaded and no wasted wording. It is efficient, though cramming four outcome categories into one clause slightly hurts scanability.

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?

For a two-parameter tool with no output schema and no annotations, the description covers what it does and how the payment is supplied but omits return behavior, error conditions, and replay semantics. It is adequate to call the tool but not complete enough to predict what happens on failure or repeat use.

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 both parameters are already documented as 'Target With Silex URL to unlock' and '64-char hex Nano mainnet send block hash', making 3 the baseline. The description adds only that txHash is transmitted via the X-Payment header, a small but real piece of 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?

Uses a specific verb ('Submit') and names the exact resource (a 64-character hex Nano mainnet send block hash) plus the concrete outcomes it buys (single drop, cross-domain synthesis, 24h JSONL stream, Whole-Keyword Pack). It is distinguishable from silex_auto_pay_and_unlock by the tx-hash input, though that contrast is only implicit and no sibling is named.

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 description implies the usage context (you already hold a Nano payment hash and want to unlock a resource), but it gives no explicit when-to-use versus when-not guidance and does not direct the agent to silex_auto_pay_and_unlock when it lacks a hash or to silex_inspect_402_challenge when it needs a challenge first. Usage is inferable rather than stated.

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