Skip to main content
Glama

Docflare

Get a document

get_document
Read-only

Gives every detail of one document: its status, who signs it and who gets a copy, each signer's progress (invited, viewed, signed or declined with the reason, reminders, delivery problems), how it was or will be sent (delivery, signing order, email, expiry, reminders, what recipients may download, which prepare_document changes for a draft), its fields with their ids and places, and the signed copy once complete. For a draft it also lists the text on its pages, the PDF's own included, and the lines a field can sit on, each with an id for edit_document, the text changes made so far, and, with page, that page's text and lines in full. Ids come from document_status.

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": {
      "id": "<id>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe document id, from document_status or the upload_document answer.
pageNoA page of a draft whose text and lines to list, with their ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds substantial transparency about what is returned: status, signers, signer progress, delivery details, fields, signed copy, and draft page text/lines. It does not describe error behavior or access prerequisites, but it goes well beyond the annotations and compensates for the absence of an output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the rest of the description is a dense, run-on enumeration with deeply nested clauses that is difficult to scan. The information is relevant, yet the lack of structure and excessive sentence length make it poorly concise.

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?

Given there is no output schema, the description carries the burden of explaining returned data, and it does so extensively, including draft-specific behavior for the page parameter. It is missing only minor operational details such as error handling or pagination, which are less critical for a read-only detail retrieval tool.

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?

Schema description coverage is 100%, so both parameters are already documented in the input schema. The description adds only modest context, reinforcing that the id comes from document_status and that the page parameter returns that page's text and lines in full. This is useful but largely overlaps the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that this tool gives every detail of one document and enumerates the returned content, including draft-specific page text and lines. It distinguishes itself from siblings by noting that ids come from document_status and that field/page ids are for edit_document, though it does not explicitly say when to prefer this over document_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: retrieve full details for a known document id, and use the page parameter for draft page text. The description references document_status as the id source but does not explicitly state when to use this tool instead of alternatives or when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources