refinery-mcp

estimate_savings

Calculate potential token savings by comparing raw HTML to cleaned text, enabling cost assessment before full processing.

Instructions

Estimate token savings from raw HTML vs cleaned text without making an Apify call.

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": {
      "raw": "<raw>",
      "cleaned": "<cleaned>"
    },
    "name": "estimate_savings"
  }
}

Input Schema

Name	Required	Description	Default
`raw`	Yes	Original raw HTML or noisy text.
`cleaned`	Yes	Cleaned text to compare against raw input.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Jul 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It states the tool does not make an Apify call, indicating it is a local computation. However, it does not mention any other side effects, required permissions, or return behavior, leaving some gaps.

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?

The description is a single, well-structured sentence that front-loads the primary purpose. Every word is necessary, and there is no redundant information.

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

Completeness2/5

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

The tool has no output schema, so the description should explain the return value (e.g., type of savings, format). It fails to do so, leaving the agent uncertain about what the tool returns. The description is too minimal for a tool with this simplicity level.

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 the schema already defines each parameter. The description adds minimal additional meaning beyond the schema, maintaining a baseline score of 3.

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 clearly states the verb 'estimate token savings' and identifies the resource ('raw HTML vs cleaned text'). The phrase 'without making an Apify call' distinguishes it from sibling tools like clean_html and clean_url, which likely involve API calls.

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?

The description implies usage context (estimating savings before deciding to clean) but does not provide explicit guidance on when to use this tool versus alternatives, nor does it state any prerequisites or exclusions.

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

Deploy Server