Strike a Block

Get depths and prices

get_pricing

Read-onlyIdempotent

The four depths a block can be struck to (8, 10, 11 or 12 leading hex zeros), each with its price in US dollars and the average time the chip needs, plus the optional printed keepsake and the line-length limit. Static information: nothing is looked up about the user and nothing is charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_pricing"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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 readOnly, idempotent, closed-world and non-destructive, so the safety profile is set. The description goes beyond them by disclosing the actual payload contents (per-depth USD price, average chip time, keepsake, line-length limit) and by confirming no user data lookup or charge occurs, which matters with no output schema.

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?

Two sentences, both earning their place: the first enumerates the return contents, the second asserts the read-only/static nature. It is somewhat list-like and could front-load 'Returns pricing for the four strike depths' for faster scanning, but there is no filler.

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?

With no parameters and no output schema, the description carries the burden of describing the response, and it does so at a reasonable level of detail. Minor gaps remain, such as units/format for the average time and whether the line-length limit is per line or total, but the shape of the result is clear.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on inputs.

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 states concretely what the tool returns: the four strike depths (8, 10, 11, 12 leading hex zeros) with their USD prices, average chip time, keepsake option and line-length limit. It implicitly distinguishes itself from compose_strike by noting nothing is charged, but it never names a sibling or says outright 'this returns a price list' in verb form.

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?

There is no explicit when-to-use statement or named alternative; the agent must infer that this is the price-check step before calling compose_strike. The phrase 'Static information: nothing is looked up about the user and nothing is charged' does imply a read-only lookup, but the routing logic is left 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?