Skip to main content
Glama

Send a draft envelope

send_envelope

Transition a draft to sent.

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>"
    },
    "name": "send_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.4/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. It does not disclose that sending is likely irreversible, that it triggers delivery to recipients, what permissions are required, or what error occurs on a non-draft envelope. Only the bare mutation is implied by "transition".

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 free of waste, but its brevity reflects under-specification rather than disciplined concision. There is no structural room for preconditions or side effects.

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 three-parameter mutation with no annotations, no output schema, and an undocumented required parameter, one short sentence is not enough. The agent is left without success/failure semantics or irreversibility warnings that the structured fields do not provide.

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 coverage is 67%: api_key and account_id are documented in the schema, but envelope_id — the only required parameter — has no description anywhere. The description adds no meaning beyond the schema, so the agent gets no clarification on the one parameter that matters.

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?

"Transition a draft to sent" names a specific state change, so the agent knows the operation's intent. However, it never names the resource as an envelope and offers nothing that separates it from siblings such as void_envelope or create_envelope, which also act on envelope lifecycle state.

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 "draft" implies a precondition, but the description states no explicit when-to-use guidance, no prerequisite that the envelope must currently be a draft, and no routing to alternatives (e.g., void versus send). An agent must infer all of this.

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