Skip to main content
Glama
Sign In
Doc Manager

Doc Manager

by giuliohome-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

search_documents

Find documents by searching titles and content with case-insensitive substring matching. Returns matched fields and snippets.

Instructions

Case-insensitive substring search across titles (always) and plaintext content. Returns id, title, encrypted flag, what matched, and a short snippet.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch term.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description must disclose behavior. It states case-insensitive substring search and lists return fields. It does not mention potential limits, pagination, or performance, but for a simple search tool the disclosure is adequate.

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 sentences, no unnecessary words. Information is front-loaded: first sentence explains functionality, second sentence lists return fields. Every piece of information serves a purpose.

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

Completeness5/5

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

Given one parameter, no output schema, and no annotations, the description covers the core functionality comprehensively. It explains what the tool does, what it returns, and its search scope. No missing critical details.

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 coverage is 100% with the 'query' parameter described as 'Search term.' The description adds that the search is across titles and content, providing context beyond the schema. This justifies a score slightly above baseline 3.

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 it performs case-insensitive substring search across titles and plaintext content, which is a distinct operation from sibling tools (CRUD, attachments). The verb 'search' and resource 'documents' are specific.

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?

It explains what is searched (titles, content) and what is returned (id, title, encrypted flag, matched field, snippet). No explicit when-not or alternative tool guidance, but sibling tools are obviously different (create, update, delete, etc.), so context provides clarity.

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