Skip to main content
Glama
Sign In
fernandogarzaaa

chimeralang-mcp

by fernandogarzaaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

chimera_compress

Compress text via contractions and symbols at light, medium, or aggressive levels. Quantum algorithm preserves key content. Returns compressed text and ratio, automatically tracking token savings to dashboard.

Instructions

Compress text via contractions/symbols. Levels: light, medium, aggressive. Returns compressed text and compression ratio. Token savings are automatically recorded to chimera_dashboard (set auto_track=false to disable). Prefer over manual regex replacement — the quantum algorithm uses structural salience so important sentences near the task focus survive compression.

Input Schema

NameRequiredDescriptionDefault
textYesText to compress
focusNoOptional task focus/query. quantum mode uses it to preserve the most relevant content.
levelNoCompression aggressiveness. Default: medium.medium
modelNoModel name used for cost tracking (e.g. 'claude-sonnet-4-6'). Default: claude-sonnet-4-6.claude-sonnet-4-6
algorithmNoCompression algorithm. quantum = structural salience compression. classic = legacy rewrite-only compression.quantum
namespaceNoCost tracker namespace (default: 'default').default
auto_trackNoAutomatically record token savings to the cost tracker (visible in chimera_dashboard). Default true.
preserve_codeNoSkip compression inside code fences (``` blocks). Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.1

TDQS

A4.4/5.0
Behavior4/5

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

Discloses automatic token tracking to chimera_dashboard with disable option, and explains quantum algorithm's preservation of important content via structural salience. No annotations present, so description carries full burden; covers compression outcomes and side effects.

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?

Very concise: three sentences cover all essential aspects without redundancy. Front-loaded with main action, then key details, then comparisons. Every sentence adds value.

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

Completeness4/5

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

Covers algorithms, levels, side effects, parameter usage. Lacks explicit output format details (beyond 'compressed text and ratio') and reversibility, but overall adequate for the tool's complexity.

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?

All 8 parameters are described in schema (100% coverage). Description adds valuable context: explains compression levels, the focus parameter for quantum mode, and the auto_track/dashboard integration. Exceeds baseline of 3 by providing operational meaning.

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?

Clearly states the tool compresses text via contractions/symbols, with specific levels (light, medium, aggressive). Distinguishes itself from manual regex replacement and implicitly from other chimera tools by mentioning quantum algorithm and structural salience.

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?

Provides guidance to prefer over manual regex replacement and explains when to disable auto_track. Mentions quantum vs classic algorithm choices but lacks explicit exclusions relative to sibling tools like chimera_log_compress.

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

Deploy Server

Other Tools