Skip to main content
Glama

Lovie Company Formation

List Open Mcp Transfer Drafts

list_open_transfer_drafts
Read-only

List the ids of the transfer drafts this user sealed that are neither spent nor expired, newest first: draft_id, status, expires_at, and approval_session_id once the phone approval was requested (empty before). A draft whose approval was rejected stays listed with status APPROVAL_REQUESTED until it expires, so never open a second approval for it; read get_transfer_draft_outcome when the user asks how it ended. Use it when the draft or approval ids from earlier in the conversation are not in front of you; the newest draft is the one they just discussed. Set include_recently_closed when the user asks how a recent transfer ended and you hold no draft_id: recently_closed then lists this user's drafts from the last 24 hours that are being sent or are no longer open, newest first, each with its status (COMMITTED sent; COMMITTING being sent right now, never send again or call it failed; REFUSED, ABANDONED, EXPIRED not sent; APPROVAL_REQUESTED not sent yet, waiting for or confirming the phone approval). Moves no money.

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

Input Schema

NameRequiredDescriptionDefault
companyIdNo
includeRecentlyClosedNo

Output Schema

NameRequiredDescriptionDefault
draftsNo
recentlyClosedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / includeRecentlyClosed
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / drafts / items / properties / status
      Added value: +{
      +  "enum": [
      +    "MCP_TRANSFER_DRAFT_STATUS_UNSPECIFIED",
      +    "MCP_TRANSFER_DRAFT_STATUS_OPEN",
      +    "MCP_TRANSFER_DRAFT_STATUS_APPROVAL_REQUESTED",
      +    "MCP_TRANSFER_DRAFT_STATUS_COMMITTING",
      +    "MCP_TRANSFER_DRAFT_STATUS_COMMITTED",
      +    "MCP_TRANSFER_DRAFT_STATUS_REFUSED",
      +    "MCP_TRANSFER_DRAFT_STATUS_ABANDONED",
      +    "MCP_TRANSFER_DRAFT_STATUS_EXPIRED"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / recentlyClosed
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "approvalSessionId": {
      +        "type": "string"
      +      },
      +      "draftId": {
      +        "type": "string"
      +      },
      +      "expiresAt": {
      +        "anyOf": [
      +          {
      +            "format": "date-time",
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "status": {
      +        "enum": [
      +          "MCP_TRANSFER_DRAFT_STATUS_UNSPECIFIED",
      +          "MCP_TRANSFER_DRAFT_STATUS_OPEN",
      +          "MCP_TRANSFER_DRAFT_STATUS_APPROVAL_REQUESTED",
      +          "MCP_TRANSFER_DRAFT_STATUS_COMMITTING",
      +          "MCP_TRANSFER_DRAFT_STATUS_COMMITTED",
      +          "MCP_TRANSFER_DRAFT_STATUS_REFUSED",
      +          "MCP_TRANSFER_DRAFT_STATUS_ABANDONED",
      +          "MCP_TRANSFER_DRAFT_STATUS_EXPIRED"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint=false, yet the description adds substantial behavior: rejected drafts remain listed as APPROVAL_REQUESTED and a second approval must never be opened, plus a per-status meaning table (COMMITTED/COMMITTING/REFUSED/ABANDONED/EXPIRED). The closing 'Moves no money' explicitly reinforces the safety profile in domain terms.

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?

Purpose and the sibling alternative are front-loaded in the first two clauses, which is correct prioritization. However it is delivered as one very long paragraph with nested clauses and some repetition of APPROVAL_REQUESTED semantics; segmenting the status meanings into a compact list would improve scanability without losing content.

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

Completeness3/5

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

For a two-parameter read-only tool with an output schema, the description covers usage, lifecycle semantics, and even return fields (redundant given the output schema). The notable gap is companyId, which is neither documented in the schema nor the text, leaving the agent to infer which company scope is queried.

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 0%, so the description must carry parameter meaning. It thoroughly explains what includeRecentlyClosed adds (last-24h closed/sending drafts with statuses), but it refers to the parameter as 'include_recently_closed' while the schema property is camelCase 'includeRecentlyClosed' — a naming mismatch that risks a malformed call. The companyId parameter is never explained at all.

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

Purpose5/5

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

States a specific verb and resource with explicit scope: lists ids of transfer drafts 'this user sealed that are neither spent nor expired, newest first', and even names the returned fields. It also distinguishes itself from the sibling get_transfer_draft_outcome, so an agent can pick it without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit triggering conditions ('when the draft or approval ids from earlier in the conversation are not in front of you') and an explicit alternative for a different user intent ('read get_transfer_draft_outcome when the user asks how it ended'). It also states when to flip include_recently_closed, so both branches of usage are covered.

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.