Skip to main content
Glama

Stringer CleanExtract

by app.getstringer
OverviewDiscussionsAdmin

Server Details

Convert public HTML or a public URL into token-dense Markdown through one remote MCP tool.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

The server exposes exactly one tool, so there is no possibility of overlapping purposes or misselection. clean_extract is clearly scoped to extraction from URLs or raw HTML.

Naming Consistency4/5

With only one tool, there is no naming inconsistency to detect, and the snake_case name is readable and descriptive. However, clean_extract is not a conventional verb_noun form, so it does not earn a perfect pattern score.

Tool Count4/5

A single tool is below the typical 3-15 range, but the server's stated purpose is a single extraction operation supporting both URL and raw HTML input. The one tool is non-trivial and well-specified, making the count slightly under but reasonable.

Completeness5/5

Within the narrow extraction domain, the tool covers both supported input types and returns the cleaned markdown plus quality diagnostics. No essential missing operation is apparent for the stated purpose.

Available Tools

1 tool
clean_extractAInspect

Extract clean, token-dense markdown from a public URL or raw HTML string. Every response reports extraction_content_ratio_band and the measurements in extraction_quality: the source-authored markdown bytes in the delivered output as a fraction of the source payload bytes, banded zero, below_threshold or at_or_above_threshold. That is a size measurement, not a statement that the page's content survived: a lightly marked-up page whose one load-bearing line was dropped scores a high band, and a faithful extraction of a navigation-heavy page scores a low one. The band is a triage hint, not a completeness guarantee. The first 3 calls are free, total, with no signup and no claim header; the allowance does not reset. Every later extraction costs USD 0.05 via x402.

ParametersJSON Schema
NameRequiredDescriptionDefault
url_or_htmlYesA public HTTP(S) URL or a raw HTML string to convert into Markdown.
max_output_bytesNoOptional maximum UTF-8 byte length of the returned Markdown.

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and excels: it discloses the quality fields, explains that the band is a size metric and not a completeness guarantee, and gives concrete cases where the band can mislead (lightly marked page with dropped line). It also exposes free allowance and per-call pricing.

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?

Purpose is front-loaded, then the metric, the caveat, and the cost are layered logically without repetition. This is long but every sentence earns its place; no filler or redundant phrasing.

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 two-parameter tool with no annotations and no output schema, the description covers the essential operating contract: input domain, output fields, interpretation pitfalls, and the x402 cost scenario. Nothing needed to invoke the tool safely is missing.

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 structured form. The description does not add new parameter-specific syntax but does provide background context about the output quality metric. Baseline of 3 is appropriate.

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: Extracts clean, token-dense markdown from a public URL or raw HTML string. Even without shaping to sibling or competing tools, the main action is fully unambiguous.

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?

The intended input and context are unmistakable (public URL or raw HTML), and the cost/free-tier detail helps callers decide whether to invoke the tool. However, there are no explicit exclusions or alternative routes, so it stays a step shy of top-score guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Removeddiagnose_extraction
  2. 1 tool update
    • Addeddiagnose_extraction
  3. 1 tool update
    • Changedclean_extract1 field changed
      • addedInput schema / properties / max_output_bytes
        Added value: +{
+  "description": "Optional maximum UTF-8 byte length of the returned Markdown.",
+  "maximum": 1048576,
+  "minimum": 1,
+  "type": "integer"
+}
  4. 1 tool update
    • Changedclean_extract3 fields changed
      • addedInput schema / additionalProperties
        Added value: +false
      • changedInput schema / properties / url_or_html / description
        Previous value: -"The public URL or raw HTML string to convert into markdown."New value: +"A public HTTP(S) URL or a raw HTML string to convert into Markdown."
      • addedInput schema / properties / url_or_html / minLength
        Added value: +1
  5. 1 tool update
    • First observedclean_extract

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources