Skip to main content
Glama

chimera_score

Score messages 0–1 for context-window compression or goal alignment. Use drop_priority to evict lowest scores, or importance_for_goal to retain messages aligned with your focus.

Instructions

Score messages 0–1 for context-window management. mode='drop_priority' (default): scores by recency+type+density — lowest scores are dropped first in lossy compression. mode='importance_for_goal': scores by alignment with the focus goal — highest scores are most relevant to keep. Vs. direct reasoning: O(n) tokenisation is far cheaper than asking the model to rank N messages, which consumes O(N*content) prompt tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messagesYesMessages to score [{role, content}]
focusNoTask focus/query. Required for importance_for_goal mode; improves drop_priority scoring.
modeNodrop_priority: score for compression — lowest scores evicted first. importance_for_goal: score by focus alignment — highest scores most relevant.drop_priority
Behavior4/5

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

With no annotations, the description carries full burden. It discloses scoring behavior (mode-dependent, O(n) efficiency) and scoring range. Minor gaps: no mention of error handling or behavior when focus is missing in importance_for_goal mode, but the schema indicates it's required.

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 three sentences, each containing essential information. It is front-loaded with the core purpose and uses no unnecessary words, making it highly concise and well-structured.

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?

Given the tool's moderate complexity (two modes, O(n) advantage) and no output schema, the description is sufficient for an agent to understand usage and behavior. It could optionally mention the return format, but the tool name implies scores.

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?

Schema coverage is 100%, so baseline is 3. The description adds extra meaning: it explains mode semantics in detail and clarifies that focus improves drop_priority scoring. This goes beyond what the schema provides.

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's purpose: scoring messages 0-1 for context-window management. It distinguishes two modes (drop_priority and importance_for_goal) and explains their use cases, making it distinct from sibling tools like chimera_compress or chimera_summarize.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use each mode (drop_priority for compression eviction, importance_for_goal for relevance retention) and compares to direct reasoning with a cost advantage. This helps an agent decide between modes and avoid alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fernandogarzaaa/chimeralang-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server