Skip to main content
Glama

split_transaction

Split a transaction across multiple categories. Provide the transactionId and an array of splits whose amounts sum to the transaction total. Replaces any existing splits on the transaction. 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": {
      "transactionId": "<transactionId>",
      "splits": "<splits>"
    },
    "name": "split_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
splitsYesSplit portions — amounts must sum to the full transaction amount
transactionIdYesID of the transaction to split

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / splits / items / properties / categoryId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / transactionId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. Changed1 schema field changed
    • changedInput schema / properties / splits / items / properties / note / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 100,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / splits / items / properties / amount / description
      Previous value: -"Amount for this split portion (decimal)"New value: +"Amount for this split portion (decimal, greater than 0)"
    • addedInput schema / properties / splits / items / properties / amount / exclusiveMinimum
      Added value: +0
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description adds to the annotations, which only declare readOnlyHint=false, by disclosing two behavioral facts: existing splits are replaced, and finance:write scope is required. Overwrite behavior is exactly the kind of destructive side effect that an agent needs to know before calling the tool. It omits what happens if the amounts do not sum correctly, that is, whether the call fails atomically or partially overwrites the existing splits; that is the main remaining gap.

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?

The description has three sentences, all of which earn their place: the operation, the input constraint, and the overwrite plus auth note. The core operation is front-loaded, and the constraints follow in the order in which the agent must satisfy them while constructing the call.

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 write tool with a nested-array parameter, no output schema, and minimal annotations, the description already covers purpose, required inputs, the summing constraint, overwrite semantics, and the auth scope. What is missing is how the tool behaves on error or conflict, for example, what happens when the amounts do not sum or a categoryId is invalid.

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%, and the schema already documents transactionId, categoryId, amount, note, and the requirement that amounts sum to the transaction total. The description restates that summing constraint but adds no syntax, format, or edge-case detail beyond what the schema provides. A baseline score of 3 is therefore appropriate.

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: 'Split a transaction across multiple categories.' That is clear enough to distinguish this tool from update_transaction or delete_split, because those tools do not state that amounts must sum to the transaction total. The description does not explicitly call out the related siblings delete_split or update_transaction, so sibling differentiation is only implicit.

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?

The description implies when to use the tool (when a single transaction must be spread across categories), and it states the key precondition that the splits must sum to the transaction total. However, it never states when not to use the tool, never names an alternative such as update_transaction or delete_split, and does not state any prerequisites beyond the finance:write scope.

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.