Skip to main content
Glama

north_stamp

Writes a SHA-256 hash to the TrueNorth chain to record that data existed at a block, enabling later verification; a small fee applies.

Instructions

Writes a SHA-256 (64 hex characters) into the TrueNorth chain, so that it can later be shown that the data existed by that block. Costs a fee of a few hundred base units. The chain is young and small: this is not proof for a court.

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": {
      "sha256": "<sha256>"
    },
    "name": "north_stamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
memoNo
sha256Yes
dry_runNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the load and does add real behavior: it is a chain write, it costs a few hundred base units, and the chain is young so the proof is not court-grade. It does not address whether the write is irreversible, whether the hash/memo becomes public, or what happens if the fee is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and immediately followed by the cost and the honesty caveat. Every sentence carries information and none restates another.

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 must carry the whole burden for a fee-charging write. It covers cost and limitations but omits the return value (a transaction or block reference), the memo's role, and dry_run behavior, leaving meaningful gaps for a mutation tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to define all three parameters and only partly does. It explains that sha256 is a 64-hex-char digest, which the schema pattern already enforces, but never explains the memo field or what dry_run does.

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?

Names a specific verb and resource: writes a SHA-256 hash into the TrueNorth chain, with the timestamping rationale ("so that it can later be shown that the data existed by that block"). That makes it unmistakable against siblings like north_fetch or north_pay, though it never names an alternative explicitly.

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?

The purpose implies the when: use it to anchor a hash for later proof of existence. It doesn't tell the agent when NOT to use it, what to do instead, or whether a related tool exists for retrieving a stamp, so the routing guidance stays implicit.

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