claude-code-docs

Overview Schema Source Related Servers Discussions Admin

Dump Index Metadata

dump_index_metadata

Inspect the complete BM25 index metadata by dumping categories, chunk IDs, headings, code literals, config keys, and distinctive terms without any parameters.

Instructions

Dump full BM25 index metadata: categories, chunk IDs, headings, code literals, config keys, and distinctive terms. No parameters.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`built_at`	Yes	DEPRECATED: Response generation time. Use index_created_at for actual index build time.
`categories`	Yes
`docs_epoch`	Yes
`index_version`	Yes
`index_created_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, but description clearly indicates a read-only dump operation with no side effects. Could mention potential performance impact or locking, but current text is adequate for a simple tool.

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?

One sentence plus 'No parameters.' Extremely concise with no wasted words. Front-loaded with main action.

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?

Given an output schema exists (not shown), description needn't detail return format. It lists what is dumped, providing sufficient context for a straightforward dump operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist; schema coverage is 100%. The description adds value by enumerating the metadata contents, exceeding the bare schema. Baseline 4 justified.

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 the tool dumps BM25 index metadata and lists specific items (categories, chunk IDs, etc.). Distinguishes from sibling tools (reload_docs, search_docs, get_status) by focusing on metadata retrieval.

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?

Implies usage when needing index metadata but does not explicitly state when to avoid or contrast with alternatives. The 'No parameters' clue helps, but lacks direct guidance.

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

Deploy Server