Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

HTML to plain text: strip HTML down to readable plain text

html_to_text
Read-only

Strip HTML to readable plain text: scripts and styles removed, block elements become line breaks, list items get bullets, entities decoded. Use to feed web content or emails to an LLM. Example: html=HiA & Bone. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesThe HTML

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses concrete output behavior (script/style removal, line breaks for blocks, bullets for list items, entity decoding) and important operational details: $0.01 per call, first 25 free, failed calls free, and repeats are charged. This aligns with and enriches the supplied readOnlyHint, openWorldHint, and idempotentHint annotations.

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?

The description is front-loaded with purpose and transformation behavior, then adds an example and pricing. It is dense but each part is useful; the pricing sentences are somewhat operational but relevant because calls are charged.

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

Completeness5/5

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

For a single-input conversion tool with annotations and no output schema, the description is complete: it explains the input example, resulting text behavior, safety profile (read-only, changes nothing), and billing implications. No critical detail for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only one parameter and 100% schema description coverage, the schema already defines the html field. The description adds practical meaning through an example showing HTML input and how entities are decoded, though it does not add format constraints beyond the schema.

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?

The description states a specific verb and resource: 'Strip HTML to readable plain text.' It also enumerates concrete transformations (scripts/styles removed, block elements become line breaks, list items get bullets, entities decoded), so an agent can tell exactly what this tool does rather than confusing it with a generic converter.

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

Usage Guidelines4/5

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

It gives clear usage context: 'Use to feed web content or emails to an LLM.' It does not explicitly compare against sibling conversion tools such as html_table_to_json, but the intended use case is clear and there is an example call.

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.