Skip to main content
Glama
moneywiz-mcp

moneywiz-mcp

by kyledh

moneywiz_get_transaction

Read-only

Retrieve a single MoneyWiz transaction by ID, including its splits, tags, and transfer links, to inspect full transaction details.

Instructions

Read one transaction, including splits, tags and transfer links.

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

Input Schema

NameRequiredDescriptionDefault
transaction_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value beyond them by disclosing the shape of the returned record (splits, tags, transfer links), which matters because there is no output schema. It omits edge behavior such as what happens for an unknown or deleted transaction_id.

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?

A single short sentence, front-loaded with the verb and the key scoping word "one", followed by the payload detail. No filler or restatement of the tool name.

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 read tool whose annotations cover the safety profile, this is nearly complete: the agent knows what it gets back and that the call is side-effect free. The remaining gaps are minor but real — no guidance on ID provenance or not-found handling.

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?

There is exactly one parameter and the schema gives it no description (0% coverage), so the description carries the burden and does not explain the expected ID format or where to obtain it. It does at least frame the call as reading one identified transaction, and the parameter name is self-evident. Minimum viable rather than compensating for the coverage gap.

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?

"Read one transaction" gives a specific verb and resource, and the word "one" implicitly separates it from the sibling list tool (moneywiz_list_transactions) that returns many. The clause about splits, tags and transfer links tells the agent what a result contains. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is the single-record fetch used when it already has an identifier, as opposed to listing or mutating. There is no explicit when-to-use, no when-not-to-use, and no pointer to moneywiz_update_transaction or moneywiz_list_transactions as alternatives.

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