Skip to main content
Glama
Sign In
DawnMCP

DawnMCP

Official
by dawnmcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

documents_search_documents

Find relevant project documentation by semantic search. Enter a query to retrieve similar documents, with optional category filtering.

Instructions

Search stored project documentation by semantic similarity.

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": {
      "query": "<query>"
    },
    "name": "documents_search_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return.
queryYesSearch query.
categoryNoFilter by category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that search is by 'semantic similarity', implying a non-keyword, vector-based search. However, it does not explicitly state that this is a read-only operation, mention rate limits, or describe side effects. The implied read-only nature of 'search' is useful but not fully transparent.

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, front-loaded sentence that states the action and scope without unnecessary words. It is appropriately concise for a simple search tool.

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, read-only search tool with fully described parameters, the description is mostly complete. It clearly identifies the resource and method. However, it does not mention result format or behavior with no results, which would be helpful but is not critical given the tool's simplicity.

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%: all three parameters (query, limit, category) have descriptions. The description adds 'semantic similarity' to explain the query's nature, but this is minimal extra value. Baseline of 3 is appropriate since the schema already documents parameters.

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 'Search' and the resource 'stored project documentation', and specifies the method 'semantic similarity'. This distinguishes it from sibling tools like documents_list_documents (which lists) and documents_add_document (which adds).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as documents_list_documents or memory_search_memory. The description does not mention exclusions, prerequisites, or preferred contexts.

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