THORChain MCP

Check Reference Memo

check_reference_memo

Read-onlyIdempotent

Pre-flight check for memoless transactions. Returns what reference would be extracted from the amount and whether it's available for registration.

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": {
      "asset": "<asset>",
      "amount": "<amount>"
    },
    "name": "check_reference_memo"
  }
}

Input Schema

Name	Required	Description	Default
`asset`	Yes	The asset (e.g. BTC.BTC)
`amount`	Yes	The transaction amount in base units

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description's added value is that it returns the would-be reference plus a registration availability verdict, but it does not say what an unavailable verdict looks like, whether an error is raised, or any rate/state constraints.

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 short sentences, front-loaded with the purpose and followed by the return semantics, with no filler. Slightly compressed to the point that the jargon is left unexpanded.

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?

With no output schema, the description must carry return-value information; it names the two things returned but not their shape or failure modes. For a small two-parameter read-only check this is adequate but leaves an agent guessing about output format.

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 both parameters are documented with examples and units, so the schema carries the load. The description only obliquely notes that the reference is derived 'from the amount', adding no format or validation detail beyond the schema.

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 ('pre-flight check' returning an extracted 'reference' and its availability), which is more than a restatement of the title 'Check Reference Memo'. It is distinguishable from the sibling tools, none of which deal with references. It falls short of 5 because the domain terms 'memoless' and 'reference' are never defined, so the exact operation is only inferable.

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?

'Pre-flight check for memoless transactions' implies the moment to call it (before registering a memoless transaction), but no alternative tool is named and there is no explicit when-not guidance. The agent must infer the workflow position from the phrase 'pre-flight'.

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

All THORChain MCP 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?