Skip to main content
Glama
ActaLumen

@actalumen/mcp-server

Official
by ActaLumen

list_documents

Lists documents in your organization to retrieve existing document IDs by name, avoiding duplicate uploads.

Instructions

List documents in the organization. Use this to find an existing document ID by name instead of re-uploading.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax documents to return (default 25).
offsetNo

Implementation Reference

  • The tool definition and handler for list_documents. The handler makes a GET request to /v1/documents with the input parameters.
    export const listDocuments = defineTool({
      name: "list_documents",
      description:
        "List documents in the organization. Use this to find an existing document ID by name instead of re-uploading.",
      inputSchema: Input,
      handler: async (input, { client }) => client.get("/v1/documents", input),
    });
  • Zod schema for input validation: optional limit (1-100, default 25) and optional offset.
    const Input = z.object({
      limit: z.number().int().min(1).max(100).optional().describe("Max documents to return (default 25)."),
      offset: z.number().int().min(0).optional(),
    });
  • Registration of listDocuments in the tools array alongside all other tools.
    export const tools: ToolDef[] = [
      uploadDocument,
      getDocument,
      listDocuments,
      listTemplates,
      startVerification,
      getVerification,
      chatWithDocument,
      getUsage,
    ];
  • The defineTool helper function used to create typed tool definitions, and the ToolDef interface that defines the structure.
    export function defineTool<Input extends z.ZodTypeAny>(t: {
      name: string;
      description: string;
      inputSchema: Input;
      handler: (input: z.infer<Input>, ctx: ToolContext) => Promise<unknown>;
    }): ToolDef {
      return t as unknown as ToolDef;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It lacks disclosure of behavioral details such as read-only nature, pagination behavior, or any rate limits. Only the basic listing action is stated.

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, direct sentences with no unnecessary information. Every word contributes to understanding the tool's purpose and usage.

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?

Adequate for a simple listing tool, but missing details like pagination behavior, result format, and any filtering capabilities beyond the schema. Given no output schema, the description could be more informative.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (limit described, offset not), and the description does not add any meaning to the parameters. It fails to explain the offset parameter or how limit/offset affect results.

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?

Clearly states it lists documents in the organization and the specific purpose of finding a document ID by name. Distinguishes from sibling tools like upload_document (re-uploading) and get_document (retrieving by ID).

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?

Explicitly advises using this tool to find an existing document ID by name instead of re-uploading, providing a clear use case. However, it does not mention when to use alternatives like get_document or list_templates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ActaLumen/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server