{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "lennney-mcp-slim-guard--recover-large-tool-results-exactly",
 "repo": "lennney/mcp-slim-guard",
 "repo_url": "https://github.com/lennney/mcp-slim-guard",
 "repo_slug": "lennney-mcp-slim-guard",
 "title": "Recover oversized MCP results without re-running calls",
 "page_title": "How to recover oversized MCP results without re-running calls with MCP Slim Guard",
 "summary": "Use result_ref and read_result to pull exact pieces of a big tool response.",
 "who": "An agent operator whose host hits context limits when an upstream tool returns a very large result.",
 "problem": "A large tool response floods the context window, and re-running the upstream call to see more of it may be costly or change the result.",
 "outcome": "The host reads the exact stored snapshot in bounded fragments or by cursor, and the upstream tool is not invoked again.",
 "steps": [
  "Run `mcp-slim-guard start` in the project so the default Compact mode is active.",
  "Make the tool call through the host and note the `result_ref` in the first response.",
  "Call `read_result` with a `query` to get up to three bounded local fragments.",
  "Or call `read_result` without `query` and follow `next_cursor` to recover the exact snapshot. Do not combine `query` with `cursor`."
 ],
 "agent_prompt": "In the lennney/mcp-slim-guard setup at <project-path>, trigger a tool call that returns a large result and capture its result_ref. Use read_result with a query to retrieve matching fragments, and confirm the fragments come from the same snapshot without a second upstream invocation.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "Recovery only works on responses that need recoverable delivery, and the README does not describe the size threshold that triggers it.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "A reviewed checkout of the lennney/mcp-slim-guard repository (0.1.1-alpha.2 is not yet published to npm)",
  "npm to run ci, build, and link the package",
  "A project directory that already has an MCP configuration",
  "An upstream MCP server definition you are authorized to use"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/lennney-mcp-slim-guard/recover-large-tool-results-exactly/",
 "md": "https://dedupedai.com/use-cases/lennney-mcp-slim-guard/recover-large-tool-results-exactly/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/lennney-mcp-slim-guard--recover-large-tool-results-exactly.json",
 "api_version": "v1"
}