Skip to main content
Glama

Compress Context

compress_context
Read-onlyIdempotent

Compress a raw conversation transcript into a structured context block that preserves user goal, decisions, and state for another AI to continue.

Instructions

Compresses a raw conversation transcript into a structured ContextBridge handoff block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerNoOptional provider override for the extraction lane: openai, openai-chat, google, groq, custom, or hosted.
transcriptYesThe raw conversation transcript to compress.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesThe user's primary goal as of the latest meaningful state in the transcript.
versionYesSchema version for ContextBridge output.
open_threadsYesUnresolved work, risks, or follow-ups that still need attention.
recent_pivotYes
current_stateYesA concise description of where the work currently stands, weighted toward the final 25% of the conversation.
key_artifactsYesImportant outputs, files, prompts, or assets mentioned in the transcript.
decisions_madeYesOnly decisions explicitly confirmed, chosen, or accepted by the user. Suggestions alone do not count.
conversation_typeYesThe dominant type of work the conversation is doing.
suggested_next_stepYesThe best immediate next action for continuing the conversation.
user_expertise_levelYesEstimated expertise level implied by the user's language and requests.
conversation_assessmentYes
constraints_and_preferencesYesImportant user preferences, constraints, or non-negotiables.
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, which cover behavioral traits. The description adds minimal extra context, only specifying the output format (ContextBridge handoff block), which is useful but not behavioral.

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 sentence of 11 words, efficiently stating the tool's purpose. It is front-loaded with the verb.

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

Completeness5/5

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

Given the simple tool with 2 parameters, full schema coverage, and an output schema present, the description is complete enough for an agent to understand the tool's function.

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?

The schema already describes both parameters with 100% coverage. The description does not add any parameter-specific information beyond what is in 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 verb 'compresses' and the resource 'raw conversation transcript' and the outcome 'structured ContextBridge handoff block'. This distinguishes it from siblings like say_hello and resume_context.

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?

The description provides no guidance on when to use this tool versus its siblings (say_hello, format_for_target, resume_context). There is no mention of prerequisites, alternatives, or when not to use it.

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/prateekg7/Context-Bridge'

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