Skip to main content
Glama
Sign In
@ledgerproof/mcp-server

@ledgerproof/mcp-server

by vsdawkins-creator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Hash an artifact (SHA-256)

ledgerproof_hash_artifact
Read-onlyIdempotent

Compute SHA-256 hash of a payload locally to preserve privacy; pass the resulting hash to issue a receipt without exposing raw data.

Instructions

Compute the SHA-256 (hex) of a payload using the SDK's hashing. PRIVACY: use this to obtain a precomputed hash so raw payloads never leave the machine — then pass the hash to ledgerproof_issue_receipt as precomputed_sha256. Over Streamable HTTP, issue_receipt REQUIRES precomputed_sha256 and rejects raw payloads, so hash locally first.

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": {
      "payload": "<payload>"
    },
    "name": "ledgerproof_hash_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesThe content to hash (UTF-8 text). Returned only as a hash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Adds context beyond annotations: local operation, privacy benefit, and that hash is returned instead of raw payload.

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 concise sentences front-loading the core function, then usage and context with no wasted words.

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?

Complete for a simple hashing tool: explains purpose, privacy, integration requirement, and the single parameter is fully documented.

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?

Schema already describes payload parameter well; description adds that hash is SHA-256 hex and its integration with issue_receipt, providing extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it computes SHA-256 hash of a payload, distinguishing it from sibling tools that handle receipts and anchors.

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

Usage Guidelines5/5

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

Explicitly describes when to use (to obtain precomputed hash for ledgerproof_issue_receipt) and why it's required over Streamable HTTP.

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

Deploy Server

Other Tools