Rosetta MCP Server

Overview Schema Source Related Servers Discussions Admin

get_cached_docs

Read-only

Search cached Rosetta CLI documentation by keyword to quickly find command-line flags and parser information. Automatically caches docs on first use.

Instructions

Search locally cached Rosetta CLI docs for a keyword. Auto-caches on first use. Use to look up command-line flags or parser info. Requires local installation.

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": "get_cached_docs"
  }
}

Input Schema

Name	Required	Description
`cache_dir`	No	Directory where docs are cached
`query`	No	Search string
`max_lines`	No	Max number of lines to return (default 200)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1May 29, 2026

TDQS

A4/5.0

Behavior3/5

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

Adds auto-caching behavior beyond annotations, which indicate readOnlyHint and openWorldHint. Could detail caching lifecycle but sufficient for basic understanding.

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 concise sentences, no wasted words. Front-loaded with primary action.

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?

Adequately describes purpose, behavior, and prerequisites. Missing expected return format for a search tool, but low complexity reduces gap.

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 covers all 3 parameters with descriptions. Description does not add additional semantic value beyond matching 'keyword' to 'query' parameter.

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?

Clearly states it searches locally cached Rosetta CLI docs for a keyword. Distinguishes from sibling tools like search_rosetta_web_docs by specifying local cached nature and CLI focus.

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?

Implies usage for looking up command-line flags or parser info, and requires local installation. Lacks explicit alternatives or when-not-to-use but provides clear context.

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