monarch-mcp

by vargahis

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_transaction_splits

Retrieve the split details of a specific transaction by providing its transaction ID.

Instructions

Get split information for a transaction.

Args: transaction_id: The ID of the transaction

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "get_transaction_splits"
  }
}

Input Schema

Name	Required	Description	Default
`transaction_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations exist to indicate behavior. The description merely states 'Get split information', implying a read operation, but omits details about authentication requirements, rate limits, or error handling (e.g., what happens if transaction_id is invalid).

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 is extremely concise, with two short sentences that state the purpose and list the parameter immediately. No extraneous words; every element serves a clear function.

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?

Given the existence of an output schema, the description need not detail return values. However, it lacks context about usage prerequisites, related tools, or behavioral specifics. For a simple retrieval tool, it is adequate but not thorough.

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?

The parameter transaction_id has no schema description (0% coverage), but the tool description provides a meaningful label ('The ID of the transaction'). This adds essential context beyond the schema's bare type declaration.

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 uses specific verb 'Get' and resource 'split information for a transaction', clearly distinguishing it from sibling tools like get_transactions or get_accounts. However, it does not elaborate on what 'split information' entails, so clarity is slightly diminished.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., get_transaction_details). It does not specify that the tool should only be used after obtaining a transaction ID, nor does it mention any conditions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.