Skip to main content
Glama

Draft Document Request

draft_document_request
Read-onlyIdempotent

Prepare a draft request for a missing financial or household document, such as a K-1, statement, trust, or property record. Returns a proposal and the X1 review destination; nothing is saved or sent. Only the supported document categories on this connection can be requested.

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": {
      "category": "<category>",
      "documentType": "<documentType>"
    },
    "name": "draft_document_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy the document is needed.
urgencyNoUse time_sensitive only when there is a real external deadline.normal
categoryYesSupported financial or household document category. This connection does not request restricted personal data.
clientIdNoTarget member user ID. Omit when the caller is preparing a request for their own household.
deadlineNoOptional ISO datetime deadline. UTC ISO 8601 ending in Z, for example 2026-10-01T09:00:00Z.
subCategoryNoSupported document subcategory, when known.
documentTypeYesHuman-readable document needed, such as 2025 K-1.
institutionOrRecipientNoOptional institution, sender, or recipient context, such as Fidelity, the CPA, or the trustee.

Output Schema

NameRequiredDescriptionDefault
draftYes
commitYes
memberYes
policyYes
statusYes
summaryYes
proposalYes
draftOnlyYes
generatedAtYes
instructionsYes
alreadyOnFileYes
appDestinationsYes
writesPerformedYes
commitBlockedReasonYes
humanSignerRequiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / subCategory / enum
      Previous value: -[
      -  "1099",
      -  "tax_return",
      -  "business_tax_return",
      -  "tax_form",
      -  "w2",
      -  "k1",
      -  "tax_payment",
      -  "charitable_receipt",
      -  "life_policy",
      -  "disability_policy",
      -  "auto",
      -  "umbrella",
      -  "commercial",
      -  "property_casualty",
      -  "will",
      -  "trust",
      -  "power_of_attorney",
      -  "beneficiary_form",
      -  "bank_statement",
      -  "brokerage_statement",
      -  "retirement_statement",
      -  "loan_statement",
      -  "equity_grant",
      -  "promissory_note",
      -  "financial_plan",
      -  "formation_document",
      -  "operating_agreement",
      -  "buy_sell",
      -  "financials",
      -  "compliance",
      -  "deed",
      -  "closing_statement",
      -  "appraisal",
      -  "lease",
      -  "property_tax"
      -]New value: +[
      +  "1099",
      +  "tax_return",
      +  "business_tax_return",
      +  "tax_form",
      +  "w2",
      +  "k1",
      +  "tax_payment",
      +  "charitable_receipt",
      +  "life_policy",
      +  "disability_policy",
      +  "auto",
      +  "umbrella",
      +  "commercial",
      +  "property_casualty",
      +  "will",
      +  "trust",
      +  "power_of_attorney",
      +  "beneficiary_form",
      +  "bank_statement",
      +  "brokerage_statement",
      +  "retirement_statement",
      +  "loan_statement",
      +  "equity_grant",
      +  "promissory_note",
      +  "financial_plan",
      +  "formation_document",
      +  "operating_agreement",
      +  "buy_sell",
      +  "financials",
      +  "compliance",
      +  "customer_acceptance",
      +  "invoice_list",
      +  "deed",
      +  "closing_statement",
      +  "appraisal",
      +  "lease",
      +  "property_tax"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: the call returns a proposal plus an X1 review destination and persists/sends nothing. That tells an agent this is a safe draft step requiring downstream review. It stops short of stating permission needs or failure modes.

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

Conciseness5/5

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

Three short sentences with zero filler. The core action leads, the no-side-effect guarantee follows immediately, and the category constraint closes it out.

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 an output schema present and full param coverage, the description need not explain return shapes, and it correctly spends its words on side-effect behavior and category constraints. It could be more complete by clarifying household-scope behavior (clientId vs. own household) or what happens on an unsupported category, but nothing essential for a correct call is missing.

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 every parameter including the enums, clientId scoping, urgency, and deadline format is already documented in the schema. The description only adds that document examples map to the category/documentType fields; it gives no additional parameter meaning, so baseline 3 applies.

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 a specific verb and resource ('Prepare a draft request for a missing financial or household document') and gives concrete examples (K-1, statement, trust, property record). It implicitly separates itself from write/submit and from list/search siblings by stating nothing is saved or sent, but it never names a sibling tool it should be preferred over.

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 by the scenario 'missing document', and one boundary is stated ('only the supported document categories on this connection can be requested'). There is no explicit when-not guidance and no pointer to alternatives such as list_document_requests or search_documents to first check whether the document already exists.

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.