Strike a Block

Verify a block's proof of work

verify_block

Read-onlyIdempotent

Independently verify one public Strike a Block block by id. Fetches the block's 80-byte header and coinbase transaction, then recomputes on this server: the double SHA-256 of the header against the recorded hash, the hash against the target in the header, the header's merkle root against the coinbase transaction, and that the inscription is inside the coinbase. Returns each check as pass or fail with the recomputed hash. Read-only; nothing is charged.

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": {
      "id": "<id>"
    },
    "name": "verify_block"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The block id: the last part of a strikeablock.com/b/<id> link (the whole link also works). Case-sensitive.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes further by naming the data fetched (80-byte header, coinbase transaction) and the four recomputations performed server-side. It also discloses the return shape (pass/fail per check plus recomputed hash) and that 'nothing is charged', which annotations do not say.

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 purpose, then the mechanics, then cost — a logical order with little waste. The closing 'Read-only; nothing is charged' partly restates readOnlyHint, though the pricing detail is new information.

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 return-value burden and does so: it enumerates the four checks and states the result format. For a single-parameter read tool, an agent has everything needed to call it and interpret the response.

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 the schema already explains the id format, link acceptance, and case-sensitivity. The description adds only the 'public' qualifier and 'one' (single block per call), which is marginal beyond the schema — the baseline 3 for full schema coverage is appropriate.

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?

States a specific verb and resource with scope: 'Independently verify one public Strike a Block block by id.' The word 'independently' hints at the distinction from a plain display tool like show_block, but the sibling is never named, so differentiation must be inferred.

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 is implied rather than stated: the agent can infer this is the tool for checking proof-of-work correctness instead of trusting the server's record. There is no explicit when-to-use/when-not framing and no named alternative (e.g., show_block for mere retrieval), leaving routing to inference.

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?