Skip to main content
Glama

Docflare

Check a document

document_status
Read-only

Tells where documents stand: draft, waiting for signatures, completed, declined or expired, with each signer's progress and, once everyone has signed, a link to the signed copy. Give the id of one document, or list them newest first, 10 a page, narrowed by status or by part of the name. The answer gives total, page and more, which is true while further pages remain.

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": "document_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe id of one document.
pageNoThe page of the list, 1 when left out.
searchNoPart of a document's name, such as "NDA".
statusNoOnly documents in this state. waiting means sent and not yet signed by everyone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds real context: the response includes per-signer progress and a signed-copy link only after all signatures. It also discloses ordering (newest first), page size (10), and the pagination flag's semantics, which annotations cannot convey.

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

Conciseness4/5

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

Three sentences, front-loaded with the outcome and followed by input modes and the response shape; little waste. The pagination sentence ("total, page and more, which is true while further pages remain") is slightly clumsy but earns its place by explaining the has-more flag.

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?

With no output schema, the description carries the return-value burden and does so: statuses, signer progress, signed-copy link, total, page, and more flag. It is nearly complete, falling short only on how it relates to the sibling get_document and whether paging applies in single-id mode.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds value the schema lacks, namely page size of 10, newest-first ordering, and that search matches part of a document's name. The id-versus-list interplay is also spelled out.

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 names the resource (documents) and a specific result (status: draft, waiting, completed, declined, expired, plus signer progress and signed-copy link). It does not, however, distinguish this from the sibling get_document, so an agent cannot tell purely from this text which one returns status versus document content.

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?

Clear operating modes are given: pass an id for one document, or omit it to list, optionally narrowing by status or partial name. There is no exclusion guidance against alternatives such as get_document, which keeps it from a 5.

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