Skip to main content
Glama
Sign In
Doc Manager

Doc Manager

by giuliohome-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

list_documents

Retrieve a list of all documents in the vault, showing each document's ID, title, encryption status, attachment status, and content size.

Instructions

List every document in the vault with its id, title, encryption status, attachment status, and content size.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It correctly describes the read-only nature by using 'list', but it does not explicitly state that the operation is non-destructive, nor does it mention performance implications or permissions. For a simple list, this is adequate but not exceptional.

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 sentence of 17 words, efficiently conveying the purpose and output. It is front-loaded with the action and immediately provides the list of fields, with no extraneous information.

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 tool with no parameters and no output schema, the description covers the essential behavior: it lists all documents and enumerates the returned fields. It does not mention pagination or behavior for empty vaults, but this is acceptable for a simple list operation.

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 input schema is empty (zero parameters) and schema description coverage is 100%, so the baseline is 3. The description does not need to explain parameters, but it does list the output fields, which marginally adds value beyond the schema.

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 action 'list every document' and specifies the exact fields returned (id, title, encryption status, attachment status, content size). This verb+resource combination is unambiguous and distinguishes the tool from siblings like 'search_documents' which likely supports filtering.

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 its siblings, particularly 'search_documents'. The description does not mention that this tool returns all documents without filtering, which could lead an agent to misuse it when a filtered query is intended.

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