Skip to main content
Glama
Sign In
mcp-Docuplete

mcp-Docuplete

Official
by Docuplete
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

list-packages

Discover available document packages in your Docuplete account. Get package IDs, names, and descriptions to pick the right one for a session.

Instructions

List all document packages configured on the Docuplete account. Returns package IDs, names, and descriptions. Use this first to discover available packages before creating a session.

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-packages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior. It mentions the return fields (IDs, names, descriptions) but does not explicitly state that this is a read-only operation or that it returns all packages without filtering. The list verb implies non-mutating behavior, adding some context but not full transparency.

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 two sentences, front-loaded with the action and resource, and includes only essential information. No redundancy or filler.

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?

For a tool with no parameters and a simple return value, the description fully covers purpose, output, and usage context. It appropriately situates the tool in the workflow relative to create-session.

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?

The tool has zero parameters, so the schema is fully complete. The description adds no parameter semantics because there are none to describe. Baseline of 4 applies for zero-parameter tools.

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 tool lists all document packages configured on the account, using a specific verb and resource. It distinguishes from siblings by focusing on package discovery rather than session or PDF operations.

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?

The description explicitly advises to use this tool first before creating a session, providing clear context. It does not name alternatives or exclusions, but the guidance is sufficient for a simple list operation.

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