Skip to main content
Glama
aibtc-mcp-server
by aibtcdev

legion_inscribe_reveal

Completes a news inscription by revealing committed content and verifying it against the derived reveal script before signing, preventing lost sats and returning the inscription ID and link.

Instructions

Complete a news inscription — STEP 2, the reveal, after the commit has confirmed.

Pass the SAME title, body and parentInscriptionId used at commit: the reveal script is derived from all three. The commit's actual output is checked against the script this content derives, so a mismatch is refused before signing rather than losing the sats.

Returns the inscription id and link for legion_propose_story.

No mainnet confirmation is asked for here, unlike the commit: those sats are already committed, and refusing the reveal would strand them rather than save them.

Requires an unlocked managed wallet.

Tip: call earning_opportunities to see how to put your assets to work.

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": {
      "commitTxid": "<commitTxid>",
      "revealAmount": "<revealAmount>",
      "title": "<title>",
      "body": "<body>"
    },
    "name": "legion_inscribe_reveal"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesSame body used in the commit step
titleYesSame title used in the commit step
feeRateNoFee rate for the reveal tx (default: medium). A number above the commit's maxRevealFeeRate is refused; a named tier is capped at it.
commitTxidYesTxid of the confirmed commit transaction
revealAmountYesrevealAmount from the legion_inscribe_story response
parentInscriptionIdNoSame parentInscriptionId used in the commit step, if any

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.77.3
    • changedInput schema / properties / feeRate / description
      Previous value: -"Fee rate for the reveal tx (default: medium)"New value: +"Fee rate for the reveal tx (default: medium). A number above the commit's maxRevealFeeRate is refused; a named tier is capped at it."
  2. First observedv1.77.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and handles it well: the reveal script is derived from the three reused fields, a mismatch is refused before signing (protecting the sats), and the sats are already committed so a refusal strands rather than saves them. Remaining gaps are the actual broadcast/finality behavior after signing and failure recovery, which it leaves implicit. This adds real value beyond structured fields but is not the full behavioral picture for a high-stakes spend.

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?

Front-loaded with the one-line purpose, then ordered as prerequisites, safety rationale, returns, and wallet requirement; each sentence earns its place except the closing 'Tip: call earning_opportunities' upsell, which is unrelated to invoking this tool and dilutes focus.

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?

No output schema exists, so the description correctly fills the gap by saying it returns the inscription id and link for legion_propose_story, and it covers the auth requirement and fee constraint. It is complete enough to invoke safely, with only post-signing failure behavior left unstated.

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%, so the schema already documents all six parameters, including the feeRate cap behavior, so the baseline is 3. The description does add meaning that the schema cannot: the three reused fields jointly derive the reveal script, so they must match the commit exactly. That is a genuine semantic contribution, but it is narrowly scoped, so a 4 is not clearly earned.

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+resource (complete/reveal a news inscription) plus an explicit statement of its place in the flow: 'STEP 2, the reveal, after the commit has confirmed.' This lets an agent distinguish it from the commit step (legion_inscribe_story) and from the unrelated proposal tool without opening a schema.

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?

Prerequisites are stated plainly: the commit must have confirmed, the same title/body/parentInscriptionId must be reused, and a managed wallet must be unlocked. It also explains why no confirmation prompt appears here, unlike the commit. It stops short of naming what to call instead when no commit exists, so not a 5.

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

Deploy Server

Other Tools