Skip to main content
Glama

unlink_transfer

Unlink transfer transactions by their shared transferId (UUID string). Both transactions in the pair will become independent income/expense entries. Use search_transactions to find the transferId of a linked pair. Requires finance:write scope.

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": {
      "transferIds": "<transferIds>"
    },
    "name": "unlink_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
transferIdsYesOne or more transferId UUID strings identifying transfer pairs to unlink

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations only supply readOnlyHint=false, so the description carries most of the burden and does add useful context: the mutation destroys the link and leaves two independent entries, and it requires finance:write scope. It does not say whether unlinking is reversible, what happens on partial/invalid IDs in a batch, or what the response returns.

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 tight sentences: action and effect first, discovery path second, permission requirement last. No redundant restatement of the tool name and nothing that could be cut without losing meaning.

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?

For a one-parameter mutation with no output schema, the description covers the effect, the identifier source, and the required scope. Only batch edge cases (multiple IDs where some are invalid) and the return value remain unaddressed.

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 100% and the schema already documents transferIds as an array of transferId UUID strings identifying pairs. The description adds only the provenance hint (obtain them via search_transactions), not format or batch-behavior detail beyond the schema, so baseline 3 applies.

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 ('Unlink transfer transactions by their shared transferId') and immediately describes the resulting state change ('Both transactions in the pair will become independent income/expense entries'), which clearly separates it from link_transfer and from the refund-link siblings.

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

Usage Guidelines4/5

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

Explicitly tells the agent where to get the required identifier ('Use search_transactions to find the transferId of a linked pair'), which is the main precondition. It does not contrast with unlink_refund or state when unlinking is inappropriate, so it stops short of full alternative routing.

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.