Skip to main content
Glama
Sign In
mcp-Docuplete

mcp-Docuplete

Official
by Docuplete
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get-session

Check the status of a document session using its token to see if it is draft, in progress, or generated, and track completion.

Instructions

Check the current status and details of a session by its token. Status is one of: 'draft' (not started), 'in_progress' (form open), or 'generated' (PDF ready). Poll this tool to check for completion.

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": {
      "token": "<token>"
    },
    "name": "get-session"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe session token returned by create-session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the status enums and frames the tool as a polling mechanism, implying read-only behavior. It doesn't explicitly state non-mutation, but the context strongly suggests a safe status check.

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 with no filler. The first sentence names the action and resource; the second provides enums and a usage tip. Perfectly front-loaded and efficient.

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 simple one-parameter status tool, this description is complete: it explains statuses, polling, and the token's origin. No output schema exists, so the description's information about status values suffices for the agent to interpret results.

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 schema already fully documents the token parameter as the session token from create-session. The description only restates 'by its token' without adding format or constraint details, so it does not elevate beyond the schema baseline.

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 checks a session's status and details by token, enumerating the three possible statuses. It distinguishes itself from list-sessions by focusing on a single session, and from get-package by being session-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?

The description explicitly says 'Poll this tool to check for completion,' providing a clear when-to-use directive. It doesn't mention alternatives or exclusions, but the polling context sufficiently guides the agent.

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