Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_api_url_to_markdown

Convert a web page URL into clean Markdown to simplify reading, archiving, or processing web content in text-based workflows.

Instructions

[Web Intelligence] Convert a web page to clean Markdown Measured p50 12 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://api.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add genuine operational context that annotations would not cover — a p50 of 12 ms and p95 of 15 ms from a dated benchmark, plus the backing endpoint host — which helps an agent reason about latency and provenance. However, it omits behaviors that matter for a network-dependent tool: whether the page is fetched live, timeout/failure behavior, payload size limits, and whether JavaScript-rendered content is included.

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?

It is a short two-sentence definition with the core action stated first and a bracketed category tag up front. The benchmark clause is dense and slightly run-on as written ('Markdown Measured p50 12 ms'), but every element carries information rather than filler.

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 one-parameter read tool this is close to adequate, and the latency benchmark plus endpoint hint nicely compensate for the absence of annotations. It still leaves the return contract unexplained (no output schema exists) and says nothing about how failures or non-HTML URLs are handled, which an agent needs before committing to a fetch.

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 there is only a single required 'url' parameter, so the schema already does the work; baseline 3 applies. The description adds no format or validity detail beyond the schema's 'Page URL' label — no scheme requirements, no note about redirects or query strings.

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?

The description gives a specific verb and resource: convert a web page URL into clean Markdown, which maps directly onto the name caelara_api_url_to_markdown. It is clear what the tool does, but it never contrasts itself with adjacent tools such as the html_to_clean_text or html_table_parser siblings, so an agent must infer the boundary on its own.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all. The description never says to prefer this over the sibling HTML/text converters, nor does it state prerequisites such as whether the URL must be publicly reachable or whether authenticated pages are supported.

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