Skip to main content
Glama

Void an envelope

void_envelope

Void a sent envelope with a reason.

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": {
      "envelope_id": "<envelope_id>",
      "reason": "<reason>"
    },
    "name": "void_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
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.
envelope_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about irreversibility, whether recipients are notified, which envelope statuses permit voiding, or what permissions are required. For a mutation tool with zero annotation coverage this is a significant gap.

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?

A single front-loaded sentence with no wasted words. It is efficiently structured, though its terseness is part of why behavioral detail is missing.

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?

A destructive mutation with no annotations, no output schema, and half its parameters undocumented needs considerably more explanation of effects, permissions, and error conditions than this one-line description provides.

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 coverage is 50%, with api_key and account_id documented in the schema and envelope_id and reason undocumented there. The description identifies the two core inputs semantically ('void a sent envelope with a reason'), slightly helping the reason parameter, but adds no format or constraint detail beyond the schema's maxLength.

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?

States a specific verb ('Void') and resource ('envelope') with a scope qualifier ('sent'), which lets an agent distinguish it from send_envelope, get_envelope, or verify_envelope. It does not explicitly name or contrast siblings, but the operation itself is unambiguous.

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?

The word 'sent' implies the envelope must already be sent, but the description never states prerequisites, when to void versus resend or request access, or what alternatives exist for envelopes in other states. No when-not guidance is given.

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