Skip to main content
Glama

List envelopes

list_envelopes

Most recent envelopes for the account.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
api_keyNoDocuflex API key (dfx_live_...). Optional if sent as the x-docuflex-api-key header.
account_idNoDocuflex account id. Optional if sent as x-docuflex-account or if the key belongs to exactly one account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full disclosure burden, and it delivers almost nothing: no default page size, no statement of what ordering "most recent" means, no maximum result behavior, no mention of what happens when status is omitted, and no error behavior for an invalid key or account. For a read/list tool with four parameters and zero annotation coverage, this leaves the agent essentially uninformed on behavior.

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

Conciseness3/5

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

The single sentence is front-loaded and contains no filler, which is good, but its brevity here reflects under-specification rather than economy. There is no structure to build on — no sentence dedicated to filtering or result limits — so the terseness costs clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with four optional parameters, no annotations, and no output schema, the definition should explain pagination limits and the status filter and note what a returned envelope looks like. It supplies none of that, leaving the agent to guess on everything except the coarse purpose.

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 description coverage is only 50%: api_key and account_id are documented in the schema, but limit and status have no descriptions anywhere. The description does not compensate at all — it never mentions filtering by status or bounding results with limit, despite those being the two parameters whose semantics an agent would most need to invoke the tool correctly.

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

Purpose3/5

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

The description names the resource (envelopes) scoped to the account and adds an ordering hint ("most recent"), so the reader knows this is a listing operation for existing envelopes rather than a create/send action. However it uses no verb and makes no attempt to distinguish itself from get_envelope or get_audit_trail, so an agent must infer that this returns a collection rather than one record.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer get_envelope for a single item, and no statement of prerequisites such as needing a valid API key or account context. The only hint toward usage is the "for the account" scoping phrase, which is implied rather than explained.

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