Skip to main content
Glama

Lovie Company Formation

Get Mcp Transfer Draft Transfer

get_transfer_draft_outcome
Read-onlyIdempotent

Read what became of a transfer draft you sealed, by draft_id: its status, the transfer_id once COMMITTED, and refusal_reason when REFUSED. Moves no money and sends nothing. Use it only when the user asks whether a transfer went through; never poll it in a loop. Report each status this way: COMMITTED means sent. COMMITTING means Lovie is sending it right now: never send it again and never tell the user it failed. REFUSED, ABANDONED and EXPIRED mean not sent. APPROVAL_REQUESTED means it is not sent yet: Lovie is waiting for or confirming the approval on the phone, so never tell the user it failed and never ask them to approve again. OPEN means the phone approval was never requested. Without a draft_id, find the draft with list_open_transfer_drafts and include_recently_closed set.

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": {
      "companyId": "<companyId>",
      "draftId": "<draftId>"
    },
    "name": "get_transfer_draft_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesUUID value wrapper.
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
statusNo
transferIdNo
refusalReasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint/idempotentHint, it discloses that no money moves and nothing is sent, that polling is inappropriate, and gives per-status behavioral obligations (COMMITTING: never resend, never report failure; APPROVAL_REQUESTED: never report failure, never re-request approval). These are operational rules an agent cannot infer from the annotations.

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?

The purpose and the no-money/no-poll constraints are front-loaded, and the status enumeration follows in a scannable parallel structure. It runs long, but nearly every clause carries a distinct instruction rather than filler.

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

Completeness5/5

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

An output schema exists, yet the description still supplies the status interpretation table that the agent needs to phrase results correctly, plus the id-recovery path. For a two-parameter read tool, nothing an agent needs to call or report it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the provenance rule for draftId (look it up via list_open_transfer_drafts with include_recently_closed). companyId receives no semantic explanation beyond the schema, which keeps this short of a 5.

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?

The opening sentence names a specific verb (read) and resource (transfer draft outcome) and enumerates exactly what is returned: status, transfer_id once COMMITTED, and refusal_reason when REFUSED. It is clearly separable from list_open_transfer_drafts, which it explicitly routes to when the id is unknown.

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?

It states the triggering condition ("only when the user asks whether a transfer went through") and an explicit prohibition ("never poll it in a loop"). It also names the alternative and the exact parameter to use when the draft_id is missing (list_open_transfer_drafts with include_recently_closed).

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.