Skip to main content
Glama

NullClear Pre-Execution Firewall & Arbiter

nullclear_read_markdown

Read-onlyIdempotent

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 (10 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. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: the <400 token output cap, the SHA-256 provenance hash, and the 10 free calls/day/IP limit. It does not say what happens on non-HTML responses, paywalled pages, or oversized documents, which is the remaining behavioral gap.

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?

Three sentences, front-loaded with the core action and output shape, then usage, then exclusions. Parenthetical details (token cap, rate limit) are dense but each carries real information; the only mild redundancy is restating the return value after already describing the conversion.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with full annotation coverage and no output schema, the description covers what it does, what it returns, output size, rate limits, and which siblings to prefer. The omission of failure/edge-case behavior (non-HTML, blocked pages, truncation) is the one thing an agent might still need.

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 the single url parameter is already documented in the schema, so the baseline is 3. The description reinforces that the URL must be public and HTTPS and must point at a webpage or documentation page rather than an API, which is mild added meaning but no format or example detail.

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?

States a specific verb and resource ('Fetch and convert any public web documentation URL or HTML article into clean, stripped Markdown') plus concrete output traits (under 400 tokens, SHA-256 hash). It explicitly separates itself from nullclear_fetch_guarded and nullclear_execute_escrow by naming the workloads those handle.

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?

Gives an explicit when-to-use list (documentation, blog posts, web pages) and an explicit when-not list (JSON REST APIs, schema-enforced x402 data endpoints needing LLM-refusal/5xx protection). It names the two alternative tools to route to instead, so no inference is required.

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.