Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_docs_html_to_clean_text

Converts HTML into readable plain text by removing scripts, styles, and tags; optionally preserves link URLs in brackets.

Instructions

[Document Utilities] Strip HTML to readable plain text, dropping scripts, styles and tags Measured p50 10 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://docs.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": {
      "html": "<html>"
    },
    "name": "caelara_docs_html_to_clean_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesHTML text
keep_linksNoAppend link URLs in brackets

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?

With no annotations, the description carries the full burden, and it does disclose useful behavior: scripts, styles and tags are dropped, plus observed latency figures and the backing endpoint. It omits auth requirements, rate limits, error behavior, and how the resulting text is normalized (entities, whitespace).

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?

Two short sentences, with the core operation front-loaded in a bracketed category prefix. The benchmark citation with date and domain is provenance noise that does not help an agent invoke the tool, but it is brief.

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 simple two-parameter tool this is close to adequate, but with no output schema the description should say more about what the returned text looks like (e.g., line-break and entity handling). The behavioral picture, particularly remote-call requirements, is only partially covered.

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%, so both parameters are already documented in the input schema. The description adds nothing about the keep_links option, so the baseline 3 applies since the schema does the work.

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 and resource ('Strip HTML to readable plain text') and names what is removed (scripts, styles, tags), which separates it from siblings like markdown_to_sanitized_html or html_table_parser. It does not explicitly name an alternative, so it stops short of full differentiation.

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, and no mention of prerequisites such as whether the HTML is passed inline versus fetched from a URL. The agent must infer that this is for extracting readable prose rather than structured data.

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