Skip to main content
Glama
deenesjakoruzh
nihar777

apollo-cache-copilot

by nihar777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

apollo-cache-copilot

CI TypeScript Tested with Vitest License: ISC MCP

Apollo InMemoryCache 정규화 결함을 진단하기 위한 AI 코파일럿 및 MCP 서버 — Apollo DevTools가 존재하지 않는 React Native를 위해 제작되었습니다.

문제

Apollo Client는 모든 결과를 __typename:id 엔티티의 평면 맵으로 정규화하고, 교차 참조를 { "__ref": "Type:id" } 포인터로 저장합니다. 이러한 정규화는 쓰기 시점에는 보이지 않으며 읽기 시점에만 실패합니다 — 대개 그 원인이 된 mutation과는 동떨어진 화면에서 말이죠. 세 가지 실패 유형이 지배적이며, 세 가지 모두 조용히(silent) 발생합니다:

결함

Apollo가 하는 일

증상

고아 포인터(Orphaned pointer) — 저장소에 User:99가 없는데 { __ref: "User:99" }가 존재

필드에 대해 undefined 반환

빈 행, 예외 없음

__typename / id 누락

캐시 키를 계산할 수 없어 객체를 인라인으로 저장

정상 렌더링, 이후 두 번째 쓰기에서 불일치 발생

타입/키 드리프트 — keyFields가 서버 페이로드와 불일치

동일한 논리 엔티티가 두 개의 키로 존재

중복된 목록 항목, 오래된 읽기

React Native는 이 모든 문제를 더 악화시킵니다:

  • Apollo DevTools 없음. 브라우저 확장 프로그램이 주요 캐시 디버거이지만 RN에는 존재하지 않습니다. 대안은 console.log(JSON.stringify(client.cache.extract()))로 수 메가바이트 덩어리를 눈으로 읽는 것입니다.

  • 영속화된 캐시. apollo3-cache-persist + AsyncStorage는 손상된 캐시가 앱 재시작 후에도 살아남게 만듭니다 — 끈적거리며, 사용자 기기에서만 재현됩니다.

  • 오프라인 우선 mutation. 낙관적 응답(optimistic responses)은 설계상 부분 엔티티를 쓰는데, 이는 정확히 결함 1과 2를 유발하는 형태입니다.

  • 긴 세션. 모바일 앱은 며칠씩 상주하므로 브라우저 탭보다 훨씬 오래 드리프트가 누적됩니다.

Related MCP server: mcp-rn-devtools

해결책

탐지는 결정적입니다. 설명은 모델의 몫입니다.

  1. 캐시 분석기 — cache.extract() 출력을 순회하며 정확한 경로(User:1.avatar → Avatar:99)와 함께 구조적 결함을 보고합니다. 단순한 그래프 순회 — 모델 없음, 추측 없음, 10MB 스냅샷에서도 실행됩니다.

  2. MCP 서버 — 해당 분석기를 개발자가 이미 사용 중인 에이전트에 노출합니다. 에이전트는 전체 캐시를 컨텍스트에 담을 필요 없이, 분석 결과와 관련 서브그래프만 요청합니다.

진단이 "10MB 덩어리를 붙여넣고 눈을 찡그리기"에서 대화로 바뀝니다.

아키텍처

flowchart TD
    subgraph client["MCP client — Claude Desktop / Cursor"]
        A["Agent (the LLM)"]
    end

    subgraph server["apollo-cache-copilot (stdio process)"]
        T["StdioServerTransport<br/>apollo-copilot mcp"]
        R["Tool registry<br/>inspect_dangling_refs<br/>patch_cache<br/>diagnose_cache_graph"]
        Z["Zod schemas<br/>parse in, shape out"]

        subgraph g["cacheAgentGraph (LangGraph, LLM-free)"]
            I["inspectorNode<br/>writes findings"]
            RE["reasonerNode<br/>writes proposedPatches"]
            P["patcherNode<br/>writes narration"]
            I --> RE --> P
        end

        TOOL1["inspectDanglingRefs()<br/>pure, on a snapshot"]
        TOOL2["patchCache()<br/>modify / evict / gc"]

        T --> R --> Z --> I
        I -.->|calls| TOOL1
        P -.->|plans for| TOOL2
    end

    A <-->|"JSON-RPC 2.0 over stdio"| T
    TOOL1 --- CACHE["cache.extract() snapshot"]
    TOOL2 --- LIVE["live ApolloCache"]

ASCII, 동일한 내용:

  MCP client (Claude Desktop, Cursor, any stdio client)
        │  JSON-RPC 2.0  ▲
        ▼   over stdio   │  stdout IS the protocol channel —
  ┌─────────────────────────────────┐   all logs go to stderr
  │ StdioServerTransport            │
  ├─────────────────────────────────┤
  │ tools: inspect_dangling_refs    │  read-only
  │        patch_cache              │  mutating (dryRun available)
  │        diagnose_cache_graph     │  read-only, plans only
  ├─────────────────────────────────┤
  │ Zod schemas — parse at the edge │
  └───────────────┬─────────────────┘
                  ▼
  ┌─────────────────────────────────────────────────────┐
  │  cacheAgentGraph  (LangGraph, deliberately LLM-free)│
  │                                                     │
  │  INSPECTOR ──────► REASONER ──────► PATCHER         │
  │  walks the store   maps findings    narrates the     │
  │  → findings[]      → patch ops      plan             │
  │      │                  │                            │
  │      │ owns `findings`  │ owns `proposedPatches`      │
  └──────┼──────────────────┼────────────────────────────┘
         ▼                  ▼
  inspectDanglingRefs()   patchCache()
  pure, on a snapshot     cache.modify / evict / gc on a live cache

각 그래프 노드는 정확히 하나의 상태 채널을 소유합니다 — 검사기(inspector)는 findings를 쓰고, 추론기(reasoner)는 proposedPatches를 쓰며, 패처(patcher)는 messages를 씁니다. messages만 누적됩니다. 노드를 다시 실행하면 동일한 캐시를 다시 분석하므로, 다른 곳에 추가하면 두 번째 실행에서 모든 finding이 중복됩니다.

그래프에 LLM이 없는 이유는 무엇인가요? 이 코파일럿이 탐지하는 모든 결함에는 기계적 복구 방법(포인터 정리, 고아 제거)이 있습니다. 모델은 switch가 이미 올바르게 처리하는 결정에 지연 시간, 비용, 비결정성을 추가할 뿐입니다. 그래프는 오케스트레이션으로서 가치가 있으며, 모델은 MCP 클라이언트에 존재하여 finding을 이를 작성한 mutation이나 fragment와 연관시킵니다.

설치

npm install @indianic/apollo-cache-copilot
# or, from a checkout
npm install && npm run build

Node.js ≥ 20 필요(vitest 4와 @langchain/core 모두 요구하며, CI는 20과 22를 포함). @apollo/client(v3.8+ 또는 v4), react, react-native는 peer 의존성입니다 — 패키지는 앱의 복사본을 사용합니다.

라이브러리 사용법

ESM 전용. 패키지에 타입이 포함되어 있습니다.

inspectDanglingRefs — 스냅샷 감사

순수하고 동기적입니다. cache.extract() 출력을 받아 findings + 통계를 반환합니다.

import { inspectDanglingRefs } from 'apollo-cache-copilot';

const { findings, stats } = inspectDanglingRefs({
  cache: client.cache.extract(),
  // all optional:
  rootIds: ['ROOT_QUERY', 'ROOT_MUTATION'], // reachability roots
  includeUnreachable: true,                  // report gc candidates
  includeNormalizationGaps: true,            // report un-keyable inline objects
});

console.log(stats);
// { entityCount: 4, refCount: 3, danglingCount: 1, unreachableCount: 1 }

for (const f of findings) {
  console.log(f.kind, f.path, f.danglingRef ?? '');
  // ORPHANED_REF  User:1.avatar  Avatar:99
  // UNREACHABLE_ENTITY  Post:7
}

Finding 종류: ORPHANED_REF, UNREACHABLE_ENTITY, MISSING_TYPENAME, MISSING_ID. 모든 finding은 정확한 캐시 경로를 포함합니다.

patchCache — 라이브 캐시에 복구 적용

연산은 선언적 설명자(descriptor)이므로 JSON 왕복에도 살아남습니다. 도구는 이를 cache.modify가 원하는 함수로 재수화(rehydrate)합니다. 순서가 있으며, 실패는 기록되며 던져지지 않으므로 배치 중간의 잘못된 키가 캐시를 반쯤 패치된 상태로 좌초시킬 수 없습니다.

import { patchCache } from 'apollo-cache-copilot';

const { dryRun, results, collected } = patchCache(client.cache, {
  operations: [
    // drop dangling refs from a list field
    { type: 'modify', id: 'User:1', fields: { posts: { action: 'PRUNE_DANGLING_REFS' } } },
    // delete / invalidate / overwrite a field
    { type: 'modify', id: 'User:1', fields: { avatar: { action: 'DELETE' } } },
    { type: 'modify', id: 'User:1', fields: { bio: { action: 'SET', value: 'unset' } } },
    // evict an entity, or one field of it
    { type: 'evict', id: 'Post:7' },
    { type: 'evict', id: 'ROOT_QUERY', fieldName: 'user', args: { id: '1' } },
  ],
  gc: true,       // run cache.gc() once, after everything lands
  dryRun: false,  // true = validate only, cache untouched
});

results.forEach((r) => console.log(r.changed, r.error ?? ''));
console.log('collected:', collected); // keys gc() removed

필드 액션: DELETE, INVALIDATE, SET(value 포함), PRUNE_DANGLING_REFS.

cacheAgentGraph — 검사 → 추론 → 계획

컴파일된 LangGraph입니다. findings, 적용할 패치 연산, 단계별 설명을 반환합니다. 절대 변경(mutate)하지 않습니다 — 검토 후 proposedPatches를 patchCache에 전달하세요.

import { cacheAgentGraph } from 'apollo-cache-copilot';

const state = await cacheAgentGraph.invoke({ cacheState: client.cache.extract() });

state.messages.forEach((m) => console.log(String(m.content)));
// 2 findings: 1 orphaned ref, 1 unreachable entity.
// ...

// Review, then apply:
patchCache(client.cache, { operations: state.proposedPatches });

또한 내보내짐: buildCacheAgentGraph()(컴파일되지 않은 빌더), 개별 노드 inspectorNode / reasonerNode / patcherNode, CacheAgentAnnotation, 모든 Zod 스키마(InspectDanglingRefsInputSchema, PatchCacheInputSchema, …) 및 그 추론 타입, 그리고 MCP 표면(createServer, startStdioServer, runInspectDanglingRefs, runPatchCache, runDiagnoseCacheGraph).

CLI 사용법

apollo-copilot [mcp]          Start the stdio MCP server (default when no args)
apollo-copilot inspect FILE   Diagnose a JSON cache snapshot and print findings

apollo-copilot inspect <file>

앱에서 캐시를 덤프한 후 읽습니다:

// in the RN app
console.log(JSON.stringify(client.cache.extract()));
npx -y -p @indianic/apollo-cache-copilot apollo-copilot inspect ./cache-snapshot.json
━━ Cache Diagnostic ━━

Entities: 4 | Refs: 3 | Dangling: 1 | Unreachable: 1

⚠  ORPHANED_REF (1)
   • User:1.avatar → Avatar:99
     Points at "Avatar:99", which is not in the cache. Reads here return undefined.

🗑  UNREACHABLE_ENTITY (1)
   • Post:7
     No root reaches this entity; cache.gc() would collect it.

깨끗한 캐시는 ✓ Cache is clean: no findings.를 출력합니다.

종료 코드: 0 성공, 1 예기치 않은 실패, 2 잘못된 입력(파일 없음, 읽을 수 없는 파일, 잘못된 JSON, 알 수 없는 명령).

apollo-copilot mcp

stdio에서 MCP 서버를 시작하고 차단합니다. MCP 클라이언트가 프로세스를 소유할 때만 유용합니다 — 아래 참조. apollo-copilot-mcp는 동일한 기능의 레거시 별칭입니다.

stdout은 프로토콜 채널입니다. 서버는 stdout에 JSON-RPC만 작성하며 모든 진단은 stderr로 갑니다. 이 경로에 console.log를 절대 추가하지 마세요.

MCP 설정

노출된 도구

도구

입력

동작

inspect_dangling_refs

cache, 선택적 rootIds / includeUnreachable / includeNormalizationGaps

읽기 전용. findings + stats 반환.

diagnose_cache_graph

cache

읽기 전용. 전체 그래프 실행. findings, proposedPatches, narration 반환. 계획만 수립.

patch_cache

cache, operations, gc, dryRun

스냅샷을 일회용 InMemoryCache로 복원하고, 패치한 후 results + 재추출된 cache를 반환.

patch_cache는 스냅샷을 전달합니다. stdio 서버에는 패처에 넘길 라이브 캐시가 없고 JSON만 있기 때문입니다. 반환된 cache를 자신의 것과 비교하거나 client.cache.restore()로 복원하세요.

모든 도구는 사람이 읽을 수 있는 요약 줄과 기계가 읽을 수 있는 structuredContent를 모두 반환하므로, 구조화된 출력을 이해하지 못하는 클라이언트도 JSON을 얻을 수 있습니다.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json(macOS) 또는 %APPDATA%\Claude\claude_desktop_config.json(Windows):

{
  "mcpServers": {
    "apollo-cache-copilot": {
      "command": "npx",
      "args": ["-y", "-p", "@indianic/apollo-cache-copilot", "apollo-copilot", "mcp"]
    }
  }
}

로컬 체크아웃에서 — 먼저 빌드(npm run build)한 후 절대 경로로 bin을 가리킵니다:

{
  "mcpServers": {
    "apollo-cache-copilot": {
      "command": "node",
      "args": ["/absolute/path/to/apollo-cache-copilot/bin/apollo-copilot.js", "mcp"]
    }
  }
}

Claude Desktop을 다시 시작합니다. 도구 메뉴 아래 세 가지 도구가 나타납니다.

Cursor

프로젝트의 .cursor/mcp.json(또는 모든 프로젝트에 대해 ~/.cursor/mcp.json):

{
  "mcpServers": {
    "apollo-cache-copilot": {
      "command": "npx",
      "args": ["-y", "-p", "@indianic/apollo-cache-copilot", "apollo-copilot", "mcp"]
    }
  }
}

로컬 체크아웃:

{
  "mcpServers": {
    "apollo-cache-copilot": {
      "command": "node",
      "args": ["${workspaceFolder}/bin/apollo-copilot.js", "mcp"]
    }
  }
}

그런 다음 Cursor → Settings → MCP에서 서버가 초록색인지 확인합니다.

그냥 물어보세요

"제 캐시 스냅샷입니다 — 프로필 화면에서 아바타가 왜 비어 있나요?"

에이전트가 diagnose_cache_graph를 호출하고, User:1.avatar → Avatar:99와 제안된 PRUNE_DANGLING_REFS를 받은 후, 엔티티 본문 없이 참조를 작성한 mutation과 연관시킵니다.

개발

npm install
npm run build      # tsc -> dist/  (run first: typecheck and tests import dist)
npm run typecheck  # tsc --noEmit -p tsconfig.test.json (includes tests)
npm test           # vitest run

tsconfig.json은 빌드용이며 __tests__ / __mocks__를 제외하므로 게시된 패키지는 도구만 포함합니다. tsconfig.test.json은 모든 것을 타입 검사하고 아무것도 생성하지 않습니다.

성공 지표

#

지표

목표

1

픽스처 스위트에 대한 탐지 재현율

100% — 시드된 모든 결함 발견

2

정상 스냅샷에 대한 오탐(false positive)

0

3

10MB extract()에 대한 분석기 런타임

< 1s

4

정확한 캐시 경로를 포함하는 findings

100%

5

증상에서 명명된 근본 원인까지의 개발자 시간

< 5분 (vs. 수 시간)

6

진단당 모델에 전송되는 토큰

< 10k — findings + 서브그래프, 전체 캐시는 절대 아님

라이선스

ISC — LICENSE 참조.

Available Tools

3 tools
diagnose_cache_graphDiagnose cache graphA
Read-only

Run the full inspect -> reason -> plan graph over a serialized cache. Returns findings, the proposed patch operations (feed them to patch_cache), and per-step narration. Plans only; never mutates.

ParametersJSON Schema
NameRequiredDescriptionDefault
cacheYesThe full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. "ROOT_QUERY", "User:1"); values are that entity's stored fields, which may contain `{ "__ref": "<cache id>" }` pointers to other entries in this same object.

Output Schema

ParametersJSON Schema
NameRequiredDescription
findingsYesEvery defect the inspector found in `cache`.
narrationYes
proposedPatchesYesMechanically-derived fixes for the fixable findings, ready to pass to patch_cache as-is.

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, and the description reinforces this with 'Plans only; never mutates.' It adds useful behavioral context about what the tool does not do and how its output should be consumed, going beyond the structured annotation without contradicting it.

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 dense sentences deliver the pipeline, the return value, the downstream consumer, and the side-effect guarantee. Every phrase earns its place and the most important behavioral constraint is front-loaded.

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?

For a single-parameter tool with a fully documented schema and an output schema, the description is complete: it names the inputs, outputs, downstream action, and non-mutating behavior. Nothing an agent needs to invoke 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?

The input schema already provides 100% coverage, including a detailed description of the cache object and its structure. The tool description does not need to restate parameter details; the schema carries the semantic weight, so the baseline score of 3 is appropriate.

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 names a specific verb and resource ('Run the full inspect -> reason -> plan graph over a serialized cache') and clearly differentiates itself from the sibling tools by describing its broader pipeline. It also states what it returns, making its role unambiguous.

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?

The description provides clear context for when this tool fits: it produces patch operations that should be fed to patch_cache, and it is a planning-only step. It does not explicitly state when to prefer it over inspect_dangling_refs, but the pipeline framing and output-to-patch_cache relationship make the usage context clear.

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

inspect_dangling_refsInspect dangling refsA
Read-only

Audit a serialized Apollo InMemoryCache (cache.extract() output) for dangling __refs, unreachable entities, and objects Apollo could not normalize. Read-only.

ParametersJSON Schema
NameRequiredDescriptionDefault
cacheYesThe full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. "ROOT_QUERY", "User:1"); values are that entity's stored fields, which may contain `{ "__ref": "<cache id>" }` pointers to other entries in this same object.
rootIdsNoCache IDs to treat as reachability roots for the UNREACHABLE_ENTITY check, e.g. ["ROOT_QUERY"]. Omit to use every one of ROOT_QUERY / ROOT_MUTATION / ROOT_SUBSCRIPTION that is present in `cache`. Has no effect on ORPHANED_REF or normalization-gap findings.
includeUnreachableNoInclude UNREACHABLE_ENTITY findings for entities no root can reach (candidates `cache.gc()` would collect). Set false to skip reachability analysis and only check refs/normalization.
includeNormalizationGapsNoInclude MISSING_TYPENAME / MISSING_ID findings for inline (non-entity) objects that Apollo could not normalize because they lack a `__typename` or an `id`/`_id` field.

Output Schema

ParametersJSON Schema
NameRequiredDescription
statsYesAggregate counts over the whole cache, independent of the findings list.
findingsYesEvery defect found, in walk order.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, and the description repeats 'Read-only.' It adds the scope of audit findings but no additional behavioral context such as error behavior, performance implications, or what the tool does not inspect. With the safety profile already covered by annotations, this is adequate but not rich.

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?

The description is two short sentences totaling 19 words. It front-loads the verb, resource, and primary finding types, and 'Read-only' is a harmless, minimal redundancy with the annotation. Every word contributes to understanding what the tool does.

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?

The tool has 4 parameters, 2 siblings, and subtle optional-parameter interactions, but the input schema is exceptionally detailed and an output schema exists, so the short description is sufficient for invocation. The main completeness gap is the lack of an explicit decision rule versus diagnose_cache_graph, preventing a 5.

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%, with detailed parameter documentation for cache, rootIds, includeUnreachable, and includeNormalizationGaps, including defaults and effects on findings. The description itself adds no parameter-level detail beyond the cache.extract() context, so the baseline of 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?

The description opens with the specific verb 'Audit' and names the exact resource: a serialized Apollo InMemoryCache from cache.extract(). It then enumerates the three distinct finding categories (dangling __refs, unreachable entities, normalization gaps), which makes the tool's scope precise and differentiates it from the write-oriented patch_cache and the broader-sounding diagnose_cache_graph.

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?

Usage is implied: use this when you have cache.extract() output and need to audit for ref/reachability/normalization issues. However, there is no explicit when-to-use versus alternatives, no exclusions, and no routing to sibling tools such as diagnose_cache_graph. The context is clear but the guidance is not explicit.

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

patch_cachePatch cacheA
Idempotent

Apply declarative repairs (modify / evict, optional gc) to a serialized cache and return the patched store. Set dryRun to validate the operations without changing anything.

ParametersJSON Schema
NameRequiredDescriptionDefault
gcNoRun `cache.gc()` once after all operations land, to collect anything the patches orphaned.
cacheYesThe full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. "ROOT_QUERY", "User:1"); values are that entity's stored fields, which may contain `{ "__ref": "<cache id>" }` pointers to other entries in this same object.
dryRunNoValidate `operations` and report what would happen without mutating the cache.
operationsYesOne or more modify/evict operations to apply, in order.

Output Schema

ParametersJSON Schema
NameRequiredDescription
cacheYesThe store after the operations landed. Unchanged when `dryRun` is true.
dryRunYesEchoes the request's dryRun — true means the cache was not actually touched.
resultsYesOne result per input operation, in the same order.
collectedYesCache keys removed by the trailing `gc()`, when it ran.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false and idempotentHint=true, and the description adds meaningful behavioral context beyond those flags: it explicitly states that dryRun validates without mutating the cache, that the modified store is returned, and that gc is optional. This goes beyond what the annotations alone convey, while not contradicting them.

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?

The description is two sentences with no filler. The core action is front-loaded, and the dryRun safety note earns its place as a critical usage caveat. It is appropriately sized for the tool's complexity.

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?

Given the very rich input and output schemas, the description only needs to establish the operation intent, the mutating nature, and the dryRun flow, which it does. The main missing element is explicit guidance on when to choose this tool over the siblings, but the schema and annotations cover most invocation details.

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 schema already thoroughly documents each parameter and nested operation shape. The description mentions modify/evict and dryRun, but it does not add parameter-level meaning beyond what the schema provides. The baseline of 3 applies because the schema carries the heavy lifting.

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 clearly states the tool applies declarative repairs (modify/evict, optional gc) to a serialized cache and returns the patched store. The specific verb 'apply' plus the resource 'serialized cache' and operation types distinguish it from the sibling tools inspect_dangling_refs and diagnose_cache_graph, which are non-mutating inspection tools.

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

Usage Guidelines2/5

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

The description implies this tool is for mutating a serialized cache and mentions dryRun for validation, but it gives no explicit guidance on when to use patch_cache versus the sibling tools. No exclusion criteria or alternative routing is provided, so an agent must infer the appropriate context from the tool name and sibling names alone.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.2
    • Changeddiagnose_cache_graph8 fields changed
      • addedInput schema / properties / cache / additionalProperties / description
        Added value: +"One normalized store entry: the raw field/value map Apollo keeps under a single cache key."
      • addedInput schema / properties / cache / description
        Added value: +"The full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. \"ROOT_QUERY\", \"User:1\"); values are that entity's stored fields, which may contain `{ \"__ref\": \"<cache id>\" }` pointers to other entries in this same object."
      • addedOutput schema / properties / findings / description
        Added value: +"Every defect the inspector found in `cache`."
      • addedOutput schema / properties / findings / items / properties / danglingRef / description
        Added value: +"The unresolved cache key the ref pointed at. Only present when kind is ORPHANED_REF."
      • addedOutput schema / properties / findings / items / properties / message / description
        Added value: +"Human-readable explanation of this finding."
      • addedOutput schema / properties / findings / items / properties / path / description
        Added value: +"Dotted path to the defect from its cache key, e.g. \"User:2.posts.1\"."
      • addedOutput schema / properties / proposedPatches / description
        Added value: +"Mechanically-derived fixes for the fixable findings, ready to pass to patch_cache as-is."
      • changedOutput schema / properties / proposedPatches / items / oneOf
        Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fields": {
-        "additionalProperties": {
-          "oneOf": [
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "DELETE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "INVALIDATE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "SET",
-                  "type": "string"
-                },
-                "value": {}
-              },
-              "required": [
-                "action",
-                "value"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "PRUNE_DANGLING_REFS",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            }
-          ]
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "id": {
-        "default": "ROOT_QUERY",
-        "type": "string"
-      },
-      "optimistic": {
-        "default": false,
-        "type": "boolean"
-      },
-      "type": {
-        "const": "modify",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id",
-      "fields",
-      "optimistic",
-      "broadcast"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "args": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fieldName": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "type": {
-        "const": "evict",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id",
-      "broadcast"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this change. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fields": {
+        "additionalProperties": {
+          "oneOf": [
+            {
+              "additionalProperties": false,
+              "description": "Remove this field from the entity entirely.",
+              "properties": {
+                "action": {
+                  "const": "DELETE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Mark this field stale so Apollo refetches it, without removing or changing its value.",
+              "properties": {
+                "action": {
+                  "const": "INVALIDATE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Overwrite this field with `value` (any JSON — a scalar, object, or `{ \"__ref\": \"<cache id>\" }`).",
+              "properties": {
+                "action": {
+                  "const": "SET",
+                  "type": "string"
+                },
+                "value": {}
+              },
+              "required": [
+                "action",
+                "value"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Drop any `__ref` pointer(s) this field holds that no longer resolve to an entity in the cache. Works on a single ref or a list of refs; refs that still resolve are left untouched.",
+              "properties": {
+                "action": {
+                  "const": "PRUNE_DANGLING_REFS",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        "description": "Map of field name -> FieldPatch describing how to change that one field.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "id": {
+        "default": "ROOT_QUERY",
+        "description": "Cache key of the entity to modify, e.g. \"User:2\". Defaults to \"ROOT_QUERY\" if omitted.",
+        "type": "string"
+      },
+      "optimistic": {
+        "default": false,
+        "description": "Apply against the optimistic layer instead of the base cache. Mirrors `cache.modify`'s option.",
+        "type": "boolean"
+      },
+      "type": {
+        "const": "modify",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id",
+      "fields",
+      "optimistic",
+      "broadcast"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "args": {
+        "additionalProperties": {},
+        "description": "Field arguments to match when evicting a specific parameterized field (used with `fieldName`).",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this eviction. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fieldName": {
+        "description": "Evict only this one field instead of the whole entity at `id`.",
+        "type": "string"
+      },
+      "id": {
+        "description": "Cache key of the entity to evict, e.g. \"Post:5\".",
+        "type": "string"
+      },
+      "type": {
+        "const": "evict",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id",
+      "broadcast"
+    ],
+    "type": "object"
+  }
+]
    • Changedinspect_dangling_refs14 fields changed
      • addedInput schema / properties / cache / additionalProperties / description
        Added value: +"One normalized store entry: the raw field/value map Apollo keeps under a single cache key."
      • addedInput schema / properties / cache / description
        Added value: +"The full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. \"ROOT_QUERY\", \"User:1\"); values are that entity's stored fields, which may contain `{ \"__ref\": \"<cache id>\" }` pointers to other entries in this same object."
      • addedInput schema / properties / includeNormalizationGaps / description
        Added value: +"Include MISSING_TYPENAME / MISSING_ID findings for inline (non-entity) objects that Apollo could not normalize because they lack a `__typename` or an `id`/`_id` field."
      • addedInput schema / properties / includeUnreachable / description
        Added value: +"Include UNREACHABLE_ENTITY findings for entities no root can reach (candidates `cache.gc()` would collect). Set false to skip reachability analysis and only check refs/normalization."
      • addedInput schema / properties / rootIds / description
        Added value: +"Cache IDs to treat as reachability roots for the UNREACHABLE_ENTITY check, e.g. [\"ROOT_QUERY\"]. Omit to use every one of ROOT_QUERY / ROOT_MUTATION / ROOT_SUBSCRIPTION that is present in `cache`. Has no effect on ORPHANED_REF or normalization-gap findings."
      • addedOutput schema / properties / findings / description
        Added value: +"Every defect found, in walk order."
      • addedOutput schema / properties / findings / items / properties / danglingRef / description
        Added value: +"The unresolved cache key the ref pointed at. Only present when kind is ORPHANED_REF."
      • addedOutput schema / properties / findings / items / properties / message / description
        Added value: +"Human-readable explanation of this finding."
      • addedOutput schema / properties / findings / items / properties / path / description
        Added value: +"Dotted path to the defect from its cache key, e.g. \"User:2.posts.1\"."
      • addedOutput schema / properties / stats / description
        Added value: +"Aggregate counts over the whole cache, independent of the findings list."
      • addedOutput schema / properties / stats / properties / danglingCount / description
        Added value: +"Of those refs, how many did not resolve."
      • addedOutput schema / properties / stats / properties / entityCount / description
        Added value: +"Total cache keys in the input."
      • addedOutput schema / properties / stats / properties / refCount / description
        Added value: +"Total `__ref` pointers encountered."
      • addedOutput schema / properties / stats / properties / unreachableCount / description
        Added value: +"Entities no root reaches."
    • Changedpatch_cache15 fields changed
      • addedInput schema / properties / cache / additionalProperties / description
        Added value: +"One normalized store entry: the raw field/value map Apollo keeps under a single cache key."
      • addedInput schema / properties / cache / description
        Added value: +"The full serialized cache, exactly as returned by `cache.extract()`. Keys are cache IDs (e.g. \"ROOT_QUERY\", \"User:1\"); values are that entity's stored fields, which may contain `{ \"__ref\": \"<cache id>\" }` pointers to other entries in this same object."
      • addedInput schema / properties / dryRun / description
        Added value: +"Validate `operations` and report what would happen without mutating the cache."
      • addedInput schema / properties / gc / description
        Added value: +"Run `cache.gc()` once after all operations land, to collect anything the patches orphaned."
      • addedInput schema / properties / operations / description
        Added value: +"One or more modify/evict operations to apply, in order."
      • changedInput schema / properties / operations / items / oneOf
        Previous value: -[
-  {
-    "properties": {
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fields": {
-        "additionalProperties": {
-          "oneOf": [
-            {
-              "properties": {
-                "action": {
-                  "const": "DELETE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "properties": {
-                "action": {
-                  "const": "INVALIDATE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "properties": {
-                "action": {
-                  "const": "SET",
-                  "type": "string"
-                },
-                "value": {}
-              },
-              "required": [
-                "action",
-                "value"
-              ],
-              "type": "object"
-            },
-            {
-              "properties": {
-                "action": {
-                  "const": "PRUNE_DANGLING_REFS",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            }
-          ]
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "id": {
-        "default": "ROOT_QUERY",
-        "type": "string"
-      },
-      "optimistic": {
-        "default": false,
-        "type": "boolean"
-      },
-      "type": {
-        "const": "modify",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "fields"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "args": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fieldName": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "type": {
-        "const": "evict",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this change. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fields": {
+        "additionalProperties": {
+          "oneOf": [
+            {
+              "description": "Remove this field from the entity entirely.",
+              "properties": {
+                "action": {
+                  "const": "DELETE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "description": "Mark this field stale so Apollo refetches it, without removing or changing its value.",
+              "properties": {
+                "action": {
+                  "const": "INVALIDATE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "description": "Overwrite this field with `value` (any JSON — a scalar, object, or `{ \"__ref\": \"<cache id>\" }`).",
+              "properties": {
+                "action": {
+                  "const": "SET",
+                  "type": "string"
+                },
+                "value": {}
+              },
+              "required": [
+                "action",
+                "value"
+              ],
+              "type": "object"
+            },
+            {
+              "description": "Drop any `__ref` pointer(s) this field holds that no longer resolve to an entity in the cache. Works on a single ref or a list of refs; refs that still resolve are left untouched.",
+              "properties": {
+                "action": {
+                  "const": "PRUNE_DANGLING_REFS",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        "description": "Map of field name -> FieldPatch describing how to change that one field.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "id": {
+        "default": "ROOT_QUERY",
+        "description": "Cache key of the entity to modify, e.g. \"User:2\". Defaults to \"ROOT_QUERY\" if omitted.",
+        "type": "string"
+      },
+      "optimistic": {
+        "default": false,
+        "description": "Apply against the optimistic layer instead of the base cache. Mirrors `cache.modify`'s option.",
+        "type": "boolean"
+      },
+      "type": {
+        "const": "modify",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "fields"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "args": {
+        "additionalProperties": {},
+        "description": "Field arguments to match when evicting a specific parameterized field (used with `fieldName`).",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this eviction. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fieldName": {
+        "description": "Evict only this one field instead of the whole entity at `id`.",
+        "type": "string"
+      },
+      "id": {
+        "description": "Cache key of the entity to evict, e.g. \"Post:5\".",
+        "type": "string"
+      },
+      "type": {
+        "const": "evict",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id"
+    ],
+    "type": "object"
+  }
+]
      • addedOutput schema / properties / cache / additionalProperties / description
        Added value: +"One normalized store entry: the raw field/value map Apollo keeps under a single cache key."
      • addedOutput schema / properties / cache / description
        Added value: +"The store after the operations landed. Unchanged when `dryRun` is true."
      • addedOutput schema / properties / collected / description
        Added value: +"Cache keys removed by the trailing `gc()`, when it ran."
      • addedOutput schema / properties / dryRun / description
        Added value: +"Echoes the request's dryRun — true means the cache was not actually touched."
      • addedOutput schema / properties / results / description
        Added value: +"One result per input operation, in the same order."
      • addedOutput schema / properties / results / items / properties / changed / description
        Added value: +"Whether `cache.modify` / `cache.evict` actually changed anything."
      • addedOutput schema / properties / results / items / properties / error / description
        Added value: +"Set when this one operation failed; the rest of the batch still ran."
      • addedOutput schema / properties / results / items / properties / operation / description
        Added value: +"The operation this result is reporting on, echoed back."
      • changedOutput schema / properties / results / items / properties / operation / oneOf
        Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fields": {
-        "additionalProperties": {
-          "oneOf": [
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "DELETE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "INVALIDATE",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "SET",
-                  "type": "string"
-                },
-                "value": {}
-              },
-              "required": [
-                "action",
-                "value"
-              ],
-              "type": "object"
-            },
-            {
-              "additionalProperties": false,
-              "properties": {
-                "action": {
-                  "const": "PRUNE_DANGLING_REFS",
-                  "type": "string"
-                }
-              },
-              "required": [
-                "action"
-              ],
-              "type": "object"
-            }
-          ]
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "id": {
-        "default": "ROOT_QUERY",
-        "type": "string"
-      },
-      "optimistic": {
-        "default": false,
-        "type": "boolean"
-      },
-      "type": {
-        "const": "modify",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id",
-      "fields",
-      "optimistic",
-      "broadcast"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "args": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "broadcast": {
-        "default": true,
-        "type": "boolean"
-      },
-      "fieldName": {
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "type": {
-        "const": "evict",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "id",
-      "broadcast"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this change. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fields": {
+        "additionalProperties": {
+          "oneOf": [
+            {
+              "additionalProperties": false,
+              "description": "Remove this field from the entity entirely.",
+              "properties": {
+                "action": {
+                  "const": "DELETE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Mark this field stale so Apollo refetches it, without removing or changing its value.",
+              "properties": {
+                "action": {
+                  "const": "INVALIDATE",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Overwrite this field with `value` (any JSON — a scalar, object, or `{ \"__ref\": \"<cache id>\" }`).",
+              "properties": {
+                "action": {
+                  "const": "SET",
+                  "type": "string"
+                },
+                "value": {}
+              },
+              "required": [
+                "action",
+                "value"
+              ],
+              "type": "object"
+            },
+            {
+              "additionalProperties": false,
+              "description": "Drop any `__ref` pointer(s) this field holds that no longer resolve to an entity in the cache. Works on a single ref or a list of refs; refs that still resolve are left untouched.",
+              "properties": {
+                "action": {
+                  "const": "PRUNE_DANGLING_REFS",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "action"
+              ],
+              "type": "object"
+            }
+          ]
+        },
+        "description": "Map of field name -> FieldPatch describing how to change that one field.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "id": {
+        "default": "ROOT_QUERY",
+        "description": "Cache key of the entity to modify, e.g. \"User:2\". Defaults to \"ROOT_QUERY\" if omitted.",
+        "type": "string"
+      },
+      "optimistic": {
+        "default": false,
+        "description": "Apply against the optimistic layer instead of the base cache. Mirrors `cache.modify`'s option.",
+        "type": "boolean"
+      },
+      "type": {
+        "const": "modify",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id",
+      "fields",
+      "optimistic",
+      "broadcast"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "args": {
+        "additionalProperties": {},
+        "description": "Field arguments to match when evicting a specific parameterized field (used with `fieldName`).",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "broadcast": {
+        "default": true,
+        "description": "Notify active queries/subscriptions of this eviction. Set false to patch silently.",
+        "type": "boolean"
+      },
+      "fieldName": {
+        "description": "Evict only this one field instead of the whole entity at `id`.",
+        "type": "string"
+      },
+      "id": {
+        "description": "Cache key of the entity to evict, e.g. \"Post:5\".",
+        "type": "string"
+      },
+      "type": {
+        "const": "evict",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "id",
+      "broadcast"
+    ],
+    "type": "object"
+  }
+]
  2. 3 tool updatesv1.0.0
    • First observeddiagnose_cache_graph
    • First observedinspect_dangling_refs
    • First observedpatch_cache
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation4/5

The three tools map to distinct workflow phases: focused read-only audit, planning/diagnosis, and mutation. inspect_dangling_refs and diagnose_cache_graph overlap in that both return findings, but the descriptions clearly differentiate the focused audit from the full inspect-reason-plan pipeline.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: inspect_dangling_refs, patch_cache, diagnose_cache_graph. The verbs and noun objects are clear and predictable.

Tool Count5/5

Three tools is a well-scoped size for a focused Apollo cache repair copilot. Each tool covers a meaningful stage of the workflow—diagnose, plan, patch—without redundancy or bloat.

Completeness5/5

The surface covers the full repair lifecycle: audit problems, generate a plan, and apply/validate repairs with dry-run and optional GC. There are no obvious dead ends for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers