context-saver-mcp

Invoke a tool without loading it

cs_call

Invoke any catalog tool by ID immediately without loading its schema into the session; pass arguments verbatim for one-off calls while preserving context.

Instructions

Invoke any catalog tool by id right now, without loading its schema into the session (arguments pass through verbatim). Prefer cs_load when you need the input schema; use cs_call for one-off calls.

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": {
      "tool": "<tool>"
    },
    "name": "cs_call"
  }
}

Input Schema

Name	Required	Description	Default
`args`	No	Arguments object forwarded to the tool
`tool`	Yes	Tool id ("server__tool")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Nov 11, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the non-obvious behavior that arguments pass through verbatim and no schema is loaded. However, it says nothing about what happens on an invalid tool id, what the return value is, or that the proxied tool may perform destructive writes — the most consequential undisclosed trait for a passthrough dispatcher.

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?

Two tight sentences with the core capability front-loaded and the routing rule second. The parenthetical about verbatim arguments is slightly buried but earns its place.

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 two-parameter passthrough with a fully documented schema and no output schema, the description covers what the agent needs to invoke it and how to choose between it and cs_load. The missing piece is return/error behavior, which is a modest gap rather than a blocking one.

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 coverage is 100%, so 'tool' and 'args' are already documented, and the id format ("server__tool") is in the schema too. The description adds only the meaningful hint that 'args' is forwarded verbatim, which is close to what the schema already conveys; baseline 3 applies.

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?

States a specific verb and resource ('invoke any catalog tool by id') plus the distinguishing mechanism ('without loading its schema into the session'), which separates it cleanly from cs_load. An agent can identify the operation and its key trait without opening the schema.

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?

Explicitly names the alternative ('Prefer cs_load when you need the input schema') and the condition selecting this tool ('use cs_call for one-off calls'). That is a direct when-to-use / when-to-use-something-else rule rather than an inference.

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

Deploy Server