context-saver-mcp

Discover downstream tools

cs_discover

List or search all tools across configured downstream MCP servers, returning IDs, source servers, and one-line descriptions without schemas to minimize tokens before loading tools.

Instructions

List or search every tool available through the gateway across all configured downstream MCP servers. Returns id, source server and a one-line description — no schemas, minimal tokens. Always do this before cs_load.

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_discover"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	Case-insensitive substring matched against tool id, description and server name
`refresh`	No	Re-connect to downstream servers and refresh the catalog cache

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Nov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (id, source server, one-line description) and the cost profile (no schemas, minimal tokens), which is the key behavioral fact for a discovery tool. It omits any note on auth requirements or how stale the catalog can get without refresh, leaving a small gap.

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?

Three short sentences: what it does, what it returns, and the required call ordering. The most decision-relevant fact (minimal tokens, no schemas) is front-loaded and nothing is redundant.

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?

There is no output schema, so the description must describe return values and it does so concretely. For a two-parameter, read-only discovery tool with full schema coverage, nothing an agent needs in order to call it correctly is missing.

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 both query and refresh are already fully documented in the schema, including the substring-matching semantics and the cache-refresh behavior. The description only echoes 'list or search' and adds no format or edge-case detail beyond that, which is the baseline for full schema coverage.

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 pair (list or search) against a precise resource (every tool available through the gateway across all downstream MCP servers) and immediately contrasts itself with cs_load by noting it returns no schemas. An agent can distinguish it from the sibling catalog without opening any schema.

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

Usage Guidelines4/5

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

It gives an explicit ordering rule — 'Always do this before cs_load' — which is exactly the routing decision an agent needs. It stops short of stating when-not to call it (e.g., when the catalog is already cached and refresh is unnecessary), so it is clear context rather than a full when/when-not/alternatives matrix.

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

Deploy Server