Skip to main content
Glama
Particle-Academy

@particle-academy/docs-mcp

Official

docs_refresh

Re-scan filesystem for docs after installing or updating a @particle-academy/* package mid-session.

Instructions

Re-scan the filesystem for docs. Call this after installing or updating a @particle-academy/* package mid-session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.ts:153-167 (registration)
    The docs_refresh tool is registered via server.registerTool with name 'docs_refresh', description, inputSchema (empty object), and handler function (lines 160-166). It calls the closure refresh() which re-scans the filesystem and updates the cache.
    server.registerTool(
      {
        name: "docs_refresh",
        description:
          "Re-scan the filesystem for docs. Call this after installing or updating a @particle-academy/* package mid-session.",
        inputSchema: { type: "object", properties: {} },
      },
      () => {
        const next = refresh();
        return textResult(
          `Re-scanned. Found ${next.length} package(s) with docs.`,
          { packageCount: next.length },
        );
      },
    );
  • The refresh closure inside registerDocsTools is the core handler logic for docs_refresh. It calls scan(options) and updates the cached PackageDocs array.
    const refresh = () => {
      cache = scan(options);
      return cache;
    };
  • The input schema for docs_refresh requires no parameters — it's an empty object schema.
    name: "docs_refresh",
    description:
      "Re-scan the filesystem for docs. Call this after installing or updating a @particle-academy/* package mid-session.",
    inputSchema: { type: "object", properties: {} },
  • src/cli.ts:96-96 (registration)
    The registerDocsTools function is invoked from the CLI entry point, tying the registration to the actual server instance.
    registerDocsTools(server, opts);
  • The McpServer.registerTool method stores the tool definition and handler in an internal Map for later dispatch via tools/call.
    registerTool(definition: ToolDefinition, handler: ToolHandler): void {
Behavior3/5

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

With no annotations, the description carries the full burden. It states that the tool re-scans the filesystem, implying a read-and-update operation. However, it does not disclose potential side effects like performance impact or cache clearing, which limits transparency.

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 a single, well-structured sentence that includes both the action and usage context. Every word adds value, and it is free of any unnecessary detail.

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?

For a simple tool with no parameters and no output schema, the description covers the core purpose and a specific use case. An explicit mention of the outcome (e.g., 'docs will be updated') would marginally improve completeness.

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?

The tool has 0 parameters and schema coverage is 100%. The description does not need to add parameter information, and its omission is appropriate. The baseline for zero parameters is 4.

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's action ('Re-scan the filesystem for docs') and includes a specific verb-resource pair. It distinguishes from sibling tools (list, list packages, read, search) by representing a refresh action.

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 explicitly provides a usage context: 'Call this after installing or updating a @particle-academy/* package mid-session.' It tells the agent when to use the tool, though it does not mention when not to use it or list alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Particle-Academy/docs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server