Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Get Transaction Details

get_transaction
Read-onlyIdempotent

Retrieve a single Firefly III transaction group and all its journal splits by transaction ID.

Instructions

Retrieve a single Firefly III transaction group and all of its journal splits by transaction ID.

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": {
      "id": "<id>"
    },
    "name": "get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe Firefly III transaction group ID.

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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context by stating that the response includes the transaction group plus all of its journal splits, which matters because there is no output schema. It omits error behavior for a missing ID, so not a 5.

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?

One sentence, front-loaded with the action and resource, with the return scope appended. Nothing is padded or redundant.

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 simple single-ID read tool with rich annotations and a fully described parameter, this is nearly complete, and it usefully compensates for the absent output schema by describing the returned group-and-splits shape. Only the not-found/error behavior is left unstated.

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?

With a single parameter at 100% schema coverage, the schema already documents that the ID is the Firefly III transaction group ID. The description repeats the notion of a transaction ID but is slightly looser than the schema's 'transaction group ID' wording, adding no real syntax or format meaning beyond the schema.

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 gives a specific verb (Retrieve) and resource (a single Firefly III transaction group) and scopes the result to include all journal splits, which clearly separates it from list_transactions and search_transactions. It stops short of naming an alternative explicitly, so it lands at 4 rather than 5.

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: 'by transaction ID' signals this is the lookup you use once you already have an ID, as opposed to listing or searching. There is no explicit when-to-use/when-not-to-use statement or named alternative, which is the gap keeping this at 3.

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