Skip to main content
Glama

bifrost-kfinance-mcp

clean_context

[$0.015 USDC] High-density HTML-to-Markdown distiller that removes scripts, styles, ads, and navigation noise while preserving pipe tables, links, and token compression metrics.

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

Input Schema

NameRequiredDescriptionDefault
htmlYesRaw HTML document to distill
max_charsNoMaximum output characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 behavioral burden. It usefully discloses that scripts, styles, ads, and navigation are stripped and tables and links are preserved, plus a $0.015 USDC cost, but it omits error behavior, truncation semantics for max_chars, and exact return structure.

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?

One dense sentence front-loads the price and then states the tool's core behavior and preservation rules. No redundant phrasing.

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 low-complexity two-parameter tool with full schema coverage, the description covers the core transformation. However, with no output schema it does not fully specify the return value or how max_chars affects output, leaving a small completeness gap.

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 html and max_chars are already documented in the schema. The description adds no parameter-level meaning beyond implying output compression; baseline 3 applies.

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 states a specific transformation (HTML-to-Markdown) and the exact noise classes removed and content preserved. It is clear what the tool does, though it does not explicitly differentiate itself from the listed siblings.

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?

No explicit when-to-use or when-not-to-use guidance, no alternatives named, and no prerequisites. The intended use is implied by the HTML-distillation purpose, but an agent gets no routing instructions.

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