Skip to main content
Glama

Convert content hashes

convert_content_hash
Read-onlyIdempotent

Convert between a content hash URI (ipfs://, ipns://, bzz://, ar://, onion3://, sia://) and the hex value stored in an ENS contenthash record (ENSIP-7), both ways, and give an HTTP gateway URL for it. Give either uri or hex. Works offline.

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": "convert_content_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexNoEncoded contenthash record value
uriNoContent URI, e.g. ipfs://bafy…

Output Schema

NameRequiredDescriptionDefault
hexYesBytes as 0x-prefixed hex
uriYes
protocolYes
gatewayUrlYesAn HTTP URL that serves the content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restatement. The description adds genuinely new behavior: conversion runs in both directions, it returns a gateway URL in addition to the converted value, and it functions without network access — context an agent cannot derive from the annotations alone.

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?

Two sentences, no repetition of the title, no filler. The accepted schemes and ENSIP-7 reference come first, the input rule and offline property follow, so the most decision-relevant facts are front-loaded.

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?

Return values are covered by an output schema, safety by annotations, and parameters by a fully described schema, so the description's burden is only the conversion contract and inputs. It delivers both, plus the offline property, leaving nothing an agent needs to call it correctly.

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 coverage is 100%, so both parameters are already documented, which sets the baseline at 3. The description earns the extra point by stating the mutual-exclusion contract ("Give either uri or hex") that the schema does not encode — there is no oneOf or required constraint, so without this sentence an agent might send both or neither.

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 gives a precise verb (convert) and a precisely bounded resource: content hash URIs in six named schemes ↔ the hex value in an ENS contenthash record, per ENSIP-7. It also states a secondary output (HTTP gateway URL), so an agent knows the tool returns more than a round-tripped string and can distinguish this from registry-oriented siblings like set_records or resolve_name.

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

Usage Guidelines4/5

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

"Give either uri or hex" is an explicit usage rule that resolves the ambiguity created by zero required parameters, and "Works offline" tells the agent not to expect a lookup against a live gateway. It stops short of naming when not to use it or pointing at an alternative, but no sibling in the list performs hash conversion, so the gap is minor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.