Fengshui Calculator

replay

Verifiability as an API call: recompute a stored request and compare its SHA-256 input digest (JCS-canonicalised) against an expected value — byte-identical reproduction or honest mismatch

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": {
      "request": "<request>"
    },
    "name": "replay"
  }
}

Input Schema

Name	Required	Description
`request`	Yes	the original kernel request JSON
`engine_version`	No	snapshot engine version; mismatch → 409-style error
`expected_input_digest`	No	64-hex SHA-256 from the report being verified

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

B3.2/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 behavioral burden. It usefully discloses JCS canonicalisation, SHA-256 digest comparison, and the 'byte-identical reproduction or honest mismatch' outcome, but it omits whether the operation is read-only, what happens on failure, and whether any side effects or permissions are involved.

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?

The definition is a single dense sentence with little wasted text. The front-loaded 'Verifiability as an API call' framing is slightly abstract, but the core operation follows immediately.

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?

There is no output schema and no annotations, so the description should carry more of the response and failure behavior. It explains the comparison concept and hints at mismatch outcomes, but does not specify the return shape or error semantics for an agent to rely on.

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 the schema already documents all three parameters. The description adds some semantic context for the digest comparison and JCS canonicalisation, but does not explain the roles of 'request' or 'engine_version' beyond what the schema provides.

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 a specific action: recompute a stored request and compare its SHA-256 input digest against an expected value. The resource and comparison target are clear, though the opening phrase 'Verifiability as an API call' is abstract and no sibling differentiation is offered.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a verification use case but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not tell an agent when this tool should be chosen over any other behavior.

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

All Fengshui Calculator 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?