Strike a Block

Preview a line on a plate

compose_strike

Read-onlyIdempotent

Preview one line of text as a Strike a Block plate, before anyone buys anything. Returns the line as it would be inscribed, the four depths (8, 10, 11 or 12 leading hex zeros) with price and average mining time, whether the line passes the public vault's content rules, and a link to checkout on strikeablock.com for each depth. In hosts that render MCP Apps it shows the plate with an editable line and a small in-frame toy miner. Read-only: nothing is struck, saved or charged; a real block is made only after the buyer checks out on strikeablock.com. A struck block is a Bitcoin-format block with real proof of work. It is not on Bitcoin's blockchain, it is not a coin or token, and it has no monetary value. Blocks at 8, 10 and 11 zeros stand alone; a 12-zero block is a link in Strike a Block's own chain.

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": {
      "text": "<text>"
    },
    "name": "compose_strike"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	The line to preview: 3 to 90 characters once runs of whitespace are collapsed. It is shown exactly as written.
`zeros`	No	Depth to highlight, as leading hex zeros: 8 (Genesis, the default), 10 (Gold), 11 (Platinum) or 12 (Prismatic).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the description reinforces this with concrete stakes: nothing is struck, saved or charged. It goes well beyond annotations by defining what a struck block is, disclaiming monetary value and blockchain status, and explaining that a 12-zero block joins Strike a Block's own chain. The only shortfall is no statement on rate limits or failure modes for rejected content.

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 purpose and return contents, then the read-only guarantee, then disambiguation. Later sentences about Bitcoin-format blocks and non-monetary value are defensive but earn their place by preventing a likely misconception; the MCP Apps rendering note is also material to expectations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden and does so: it enumerates the return payload (inscribed line, four depths with price and average mining time, content-rule verdict, checkout links per depth) and notes the interactive rendering where supported. Nothing an agent needs to call it or interpret results is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it enumerates the four depth values and explains the consequence of each (8/10/11 stand alone, 12 links into the chain), which the schema only labels as names. It also clarifies that the line is rendered exactly as written and checked against the public vault's content rules.

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?

States a specific verb and resource ("Preview one line of text as a Strike a Block plate") and immediately scopes it ("before anyone buys anything"). This is clearly distinguishable from browse_vault, get_pricing, show_block and verify_block, which browse, price, display or verify rather than preview an unstruck line.

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?

Signals the usage context explicitly: preview before a purchase, with a real block made only after checkout on strikeablock.com. It does not name a sibling as the alternative for related tasks (e.g. pricing or verification), so the routing guidance is contextual rather than explicit.

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

All Strike a Block tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?