Skip to main content
Glama
Sign In
docs-mcp-server

docs-mcp-server

by arabold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_docs

Destructive

Deletes indexed documentation for a specified library and version from the search index. Use it to clear stale or unwanted entries only when explicitly instructed.

Instructions

Remove indexed documentation for a library version. Use only if explicitly instructed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "library": "<library>"
    },
    "name": "remove_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
libraryYesLibrary name.
versionNoLibrary version (optional, removes latest if omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.4.1

TDQS

A3.8/5.0
Behavior3/5

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

The destructiveHint=true annotation already tells the agent this is a destructive operation, so the description's main added value is the clarifying scope: it removes the index entry for a library/version rather than source content. It does not state whether the data is recoverable, whether re-scraping restores it, or how it affects concurrent jobs or search results.

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 short sentences: the action first, then the caution. No redundant restatement of the title or the parameters, and the most safety-relevant instruction is placed early.

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 two-parameter, non-output-schema tool, the description plus annotations cover purpose, scope, and caution adequately. It could go further by noting what happens to already-indexed pages or that the operation must be undone by re-scraping, but no critical calling information 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?

Schema description coverage is 100%, and the schema already documents that version is optional and defaults to the latest. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Remove indexed documentation') scoped to 'a library version', which is enough to distinguish it from read-oriented siblings like scrape_docs, search_docs, and read_page. It stops short of naming an alternative or explaining how the indexed docs relate to other tools, so it is clear but not fully differentiated.

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?

'Use only if explicitly instructed' gives an explicit negative condition that strongly gates invocation, which is valuable for an irreversible operation. There is no positive statement of when it is the right tool versus an alternative, so the guidance is one-sided but actionable.

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