Skip to main content
Glama
NullClear — Web3 Security & Tx Decoder

NullClear — Web3 Security & Tx Decoder

Official

nullclear_read_markdown

Read-onlyIdempotent

Fetches public documentation or HTML articles and converts them into clean, token-limited Markdown with a SHA-256 content hash. Use it to read docs or blog posts while minimizing context-window noise.

Instructions

Fetch and convert any public web documentation URL or HTML article into clean, stripped Markdown (<400 tokens) with a SHA-256 content hash. Use this when reading documentation, blog posts, or web pages while minimizing context-window noise (100 free calls/day/IP). Returns markdown body and provenance hash. Do NOT use for JSON REST APIs or schema-enforced x402 data endpoints needing LLM-refusal/5xx protection (use nullclear_fetch_guarded or nullclear_execute_escrow).

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": {
      "url": "<url>"
    },
    "name": "nullclear_read_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS webpage or documentation URL to extract into clean Markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, but the description adds context the annotations cannot: an output size cap of under 400 tokens, a SHA-256 provenance hash returned with the body, and a rate limit of 100 free calls/day/IP. Together these make the tool's cost, size, and safety profile clear, which is valuable context.

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 description is dense but well structured: capability and output come first, usage and the rate limit come second, and the exclusion and alternatives come last. Each sentence earns its place, though the final clause is packed with jargon ('LLM-refusal/5xx protection') that slightly reduces readability.

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?

This is a simple single-parameter read tool with rich annotations and no output schema. The description nonetheless covers output format, size bound, return fields, rate limits, and exclusions, so an agent has everything needed to call it correctly.

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?

Only one parameter exists and the schema provides 100% coverage of its description, so the schema already does the work; this sets the baseline at 3. The description adds the constraint that the URL must be public and the target must be HTML or documentation, but gives no syntax or format details beyond that.

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 opens with a specific verb-plus-resource ('Fetch and convert any public web documentation URL or HTML article') and names the exact output ('clean, stripped Markdown (<400 tokens) with a SHA-256 content hash'). It is clearly distinguishable from siblings like nullclear_fetch_guarded or nullclear_execute_escrow, which are explicitly reserved for JSON/x402 endpoints.

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?

It states when to use this tool (reading documentation, blog posts, or web pages while minimizing context-window noise) and when not to use it, naming the two alternative tools by name and giving the condition that selects them ('JSON REST APIs or schema-enforced x402 data endpoints needing LLM-refusal/5xx protection'). This is explicit when/when-not/alternatives guidance.

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