Skip to main content
Glama
Sign In
claude-code-docs

claude-code-docs

by jpsweeney97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reload Claude Code Docs

reload_docs

Refresh the documentation search index after making edits to ensure changes are indexed.

Instructions

Force reload of Claude Code documentation. Use after editing docs to refresh search index.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, so description must disclose behavioral traits. It only says 'Force reload', which implies a destructive or disruptive action but does not explain potential side effects (e.g., temporary search unavailability, auth requirements, or whether it is idempotent).

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 efficient sentences, front-loaded with purpose, no wasted words.

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 zero parameters and no output schema, the description covers the action and when to use it. Could mention if it blocks or returns a status, but overall adequate.

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?

Schema has zero parameters (100% coverage), so description need not add parameter details. Baseline score 4 is appropriate with no parameters to document.

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?

Description clearly states the verb 'Force reload' and the resource 'Claude Code documentation'. It distinguishes from siblings by specifying the purpose is to refresh the search index after editing docs.

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?

Explicitly says 'Use after editing docs to refresh search index', providing a clear context. While it doesn't mention alternatives, the sibling tools suggest other actions like searching or status checks.

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

Deploy Server

Other Tools