Skip to main content
Glama
Sign In
HomarUScc

HomarUScc

by kcdjmaxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

docs_clear

Clear a documentation domain by domain name, removing all indexed content. Use to reset or delete a domain's documentation data.

Instructions

Clear a documentation domain, removing all indexed content.

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": {
      "domain": "<domain>"
    },
    "name": "docs_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to clear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior3/5

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

Without annotations, the description carries the burden of behavioral disclosure. It does state 'removing all indexed content', which indicates a destructive operation, but it does not mention irreversibility, permission requirements, or any side effects on related data.

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, concise sentence that effectively communicates the tool's purpose without unnecessary words. It is front-loaded and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter destructive operation, the description covers the core semantics but lacks details on success/failure behavior or consequences. Given the existence of the sibling tool docs_clear_compiled, some differentiation would improve completeness.

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 schema description coverage is 100%, so the parameter 'domain' is fully documented. The description does not add additional meaning beyond the schema, which is acceptable given the high coverage.

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 verb 'Clear' and the resource 'documentation domain', and specifies the effect 'removing all indexed content'. This distinguishes it from the sibling tool docs_clear_compiled, which likely clears a subset of content.

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?

The description provides a clear action but does not explicitly state when to use this tool versus alternatives like docs_clear_compiled. Usage context is implied by the description's meaning, but no exclusions or alternative guidance are provided.

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