Skip to main content
Glama
Sign In
context-saver-mcp

context-saver-mcp

by renniyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Unload tools to reclaim context

cs_unload

Unload previously loaded downstream tools by ID or glob pattern, or omit tools to release all tools loaded in the current session and reduce context usage.

Instructions

Unload previously loaded downstream tools. Omit "tools" to unload everything loaded this session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cs_unload"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsNoLoaded tool ids (or glob patterns) to unload; omit for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the key scope ('previously loaded downstream tools' and 'this session') and the omit-all default, but it does not explain reversibility, error behavior, or side effects beyond the schema.

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?

Two short sentences, front-loaded with the main action and followed by the key default. There is no unnecessary wording.

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?

For a low-complexity tool with one optional parameter and no output schema, the description covers the purpose and default scope sufficiently. Minor gaps remain around edge cases and side effects, but they do not prevent correct invocation.

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?

Schema description coverage is 100%, so the input schema already documents the sole optional 'tools' parameter. The description reinforces the omit behavior and adds session scope, but does not add significant meaning 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 uses a specific verb and resource: 'Unload previously loaded downstream tools.' This clearly distinguishes the action from siblings such as cs_load, and the default behavior clarifies scope.

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

Usage Guidelines3/5

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

It implies when to use the tool by describing unloading previously loaded tools and the omit-all behavior, but it does not explicitly state when to choose this over alternatives or mention exclusions or prerequisites.

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