Skip to main content
Glama
CrispParse MCP Server

CrispParse MCP Server

Official

crispparse_extract

Extract clean Markdown or structured JSON from public URLs to convert web pages into LLM-ready content for analysis and retrieval.

Instructions

Extract clean, LLM-ready Markdown or structured JSON from any public URL using CrispParse.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe full http:// or https:// URL to extract.
modeNoOutput format (defaults to markdown).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does not meet it. It says nothing about JavaScript rendering, rate limits, content size caps, failure modes for unreachable URLs, or whether the 'structured JSON' output follows a defined schema.

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?

A single front-loaded sentence that names the capability, the inputs, the outputs, and the engine with zero filler. Nothing is repeated from the schema and nothing could be trimmed without losing signal.

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?

For a low-complexity, two-parameter tool this covers the essentials, but with no output schema the description should at least sketch what 'structured JSON' contains. The absence of any note on extraction limits or failure behavior leaves a gap for an agent planning a call against an arbitrary URL.

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 description coverage is 100% and includes an enum on mode, so the schema already documents both parameters fully. The description's 'Markdown or structured JSON' mirrors the mode enum without adding format details, and 'any public URL' adds only a mild constraint on the url parameter — the baseline 3 is appropriate.

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?

States a specific verb ('Extract') and concrete outputs ('Markdown or structured JSON') from a defined input scope ('any public URL'), naming the backing service CrispParse. An agent knows immediately what the tool produces, though there are no sibling tools to differentiate against.

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 phrase 'any public URL' implies a boundary — non-public or authenticated pages are presumably out of scope — and the mode parameter hints at a format choice. But there is no explicit when-to-use vs. when-not guidance, no mention of alternatives, and no stated prerequisites.

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