Skip to main content
Glama

ninerouter_compact_response

Compacts an OpenAI Responses conversation through 9Router by submitting a model and request object, helping shrink long context for follow-up calls.

Instructions

Compact an OpenAI Responses conversation through 9Router.

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": {
      "model": "<model>",
      "request": "<request>"
    },
    "name": "ninerouter_compact_response"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
requestYesOpenAI Responses compaction fields, including input.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds no behavioral context beyond the purpose, such as whether the original conversation is preserved or mutated, what compaction produces, or any authentication or rate-limit requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler or redundant wording. It is appropriately terse, though its brevity contributes to the larger completeness gaps handled in other dimensions.

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?

This is a non-read-only tool with a nested request object and no output schema, so the description should clarify return behavior and operational effects. It omits what compaction returns, how the original conversation is affected, and how the model/request parameters should be formed.

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?

The input schema partially describes the nested 'request' object but leaves 'model' undocumented, and the description adds no parameter meaning at all. With schema description coverage at 50%, the description does not compensate for the missing guidance on model selection or compaction request fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb, 'Compact', and a specific resource, 'OpenAI Responses conversation', with the '9Router' provider context. It does not differentiate this compaction operation from sibling chat or token-counting tools, so sibling selection remains partly inferred.

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?

There is no explicit guidance on when to use compaction, when not to use it, or which sibling tool to choose instead. An agent must infer that this is for reducing conversation context, with no prerequisites or exclusions provided.

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