$Refract$

Refract

get_compressed

Reduce token count of Python or JS/TS source files by stripping function bodies while retaining signatures and contracts, and return compression stats.

Instructions

S5-compress a single source file — Python or JS/TS (signatures + dependency contracts, bodies stripped) — and return the compressed structure plus token stats (tokens_before, tokens_after, reduction_pct).

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": {
      "file_path": "<file_path>"
    },
    "name": "get_compressed"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Path to a .py file (relative to --root or absolute).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Jul 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so the description must disclose behaviors. It does not state whether the operation is read-only or modifies files, nor does it mention side effects, auth requirements, or rate limits. The word 'compress' might imply mutation, but the return of a 'compressed structure' suggests the original file is unchanged. This ambiguity is a gap.

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. It front-loads the action ('S5-compress a single source file'), specifies file types, details the compression behavior, and lists the output. No unnecessary words.

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?

Without output schema, the description should explain the return value structure, but it does mention 'compressed structure plus token stats (tokens_before, tokens_after, reduction_pct),' which is helpful. However, it lacks behavioral context (read/write), does not resolve the file type inconsistency, and does not address how this relates to sibling tools like 'expand.' The minimal viable information is present, but gaps reduce completeness.

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

Parameters2/5

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

Schema coverage is 100% (one parameter with description). The description adds that the tool supports Python and JS/TS, but the schema's parameter description says 'Path to a .py file,' which contradicts the broader file types stated in the tool description. This inconsistency misleads the agent and detracts from the value added 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 clearly states the tool compresses a single source file (Python or JS/TS) by stripping bodies while keeping signatures and dependency contracts, and returns token stats. The verb 'compress' and resource 'source file' are specific, and it distinguishes from siblings like 'blast_radius' or 'expand' implicitly.

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 guidance on when to use this tool versus alternatives. The description does not mention when to choose compression over expansion or other sibling tools, leaving the agent without decision context.

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

Deploy Server