Skip to main content
Glama

Caelara Labs Document Utilities

html_to_clean_text

Strip HTML to readable plain text, dropping scripts, styles and tags

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": "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 observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It does disclose that scripts, styles and tags are dropped — useful information about what content is lost — but says nothing about whitespace collapsing, HTML-entity decoding, handling of malformed markup, or what the returned string looks like.

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 with zero filler: the verb, source format, target format, and dropped content all appear before any trailing clause. Nothing could be removed without losing information.

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 two-parameter, annotation-free pure conversion tool with no output schema, the definition covers purpose and dropped content sufficiently to invoke it correctly. The only real gap is output-shape detail (whitespace normalization, link rendering), which is minor for a deterministic converter.

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%, so both parameters are already documented in the schema and the baseline of 3 applies. The description adds no parameter-level meaning and in particular never mentions keep_links or how link URLs are rendered, which the schema only summarizes as 'Append link URLs in brackets'.

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 ('Strip') and resource ('HTML to readable plain text') and further narrows scope by naming what is discarded: scripts, styles and tags. It is clearly distinguishable from the sibling converters (markdown, XML, CSV) by input type, though it never explicitly contrasts itself with them.

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?

Usage is implied rather than stated: an agent can infer this is the tool for HTML input needing plain-text output. There is no explicit when-to-use statement, no prerequisites, and no mention of when an alternative (e.g., markdown_to_sanitized_html) would be preferred.

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.

Resources