Skip to main content
Glama

Lovie Company Formation

Request Transfer Approval

request_transfer_approval

Send the trusted-device approval for a sealed draft to the user's phone and return its approval_session_id. Tell the user to answer on their phone within ~5 minutes. Once they approve there, Lovie sends the transfer by itself and notifies them of the result; you send nothing, and you must not ask the user to come back and report the approval. If the user later asks what happened, call get_transfer_draft_outcome with the draft_id. If they reject or let the approval expire, nothing is sent.

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": "request_transfer_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdNo
companyIdNo

Output Schema

NameRequiredDescriptionDefault
expiresAtNo
approvalSessionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

The annotations only declare openWorldHint=false and destructiveHint=false, so the description carries the behavioral burden and does so well. It discloses the out-of-band flow to the user's phone, the approximate five-minute expiry window, that Lovie itself sends the transfer and notifies the user on approval, and that a rejection or expiry results in nothing being sent.

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 imperative action is front-loaded, then the user-facing instruction, then the follow-up routing and the failure case. Every sentence carries information, though the repeated emphasis on not sending anything is slightly verbose.

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?

An output schema exists, so the returned approval_session_id need not be expanded, and the description covers the full lifecycle of the approval. The only gap is the unexplained companyId, which an agent must pass without knowing its role.

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 0% with two parameters, so the description must compensate. It references the draft_id in the follow-up context, which implies the draft identity drives the approval, but it says nothing about companyId or why either identifier is needed. Partial compensation only.

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?

A specific verb and resource: send the trusted-device approval for a sealed draft to the user's phone and return an approval_session_id. That is clearly distinguishable from siblings such as get_transfer_draft_outcome (which reports an outcome) and mcp_draft_transfer (which creates the draft).

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 when to use the tool, that the user must answer within roughly five minutes, an explicit alternative for later follow-up (get_transfer_draft_outcome with the draft_id), and a negative instruction not to ask the user to come back and report the result. When-not guidance is also present: on rejection or expiry nothing is sent.

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.