Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Search Accounts

search_accounts
Read-onlyIdempotent

Find Firefly III accounts by name, account number, IBAN, or ID, and filter by account type or field to locate the right account.

Instructions

Search Firefly III accounts by name, account number, IBAN, or 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": {
      "query": "<query>"
    },
    "name": "search_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
typeNoOptional account type filter (e.g. 'asset', 'expense', 'revenue', 'liability').
fieldNoWhich account field to match against (defaults to 'name').name
limitNoItems per page.
queryYesSearch keyword or value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare this is a read-only, idempotent, non-destructive open-world search. The description adds the searchable account fields but does not disclose pagination behavior, result ordering, or case sensitivity beyond what the schema and annotations provide.

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 definition is a single front-loaded sentence with no redundant wording. It is appropriately sized for a simple search tool.

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?

This is a simple search tool with full schema coverage, detailed annotations, and no output schema, so the description does not need to explain return values. It is nearly complete, with the main gap being explicit routing guidance against sibling account-listing and account-retrieval tools.

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%, so the schema already documents all five parameters, including the field enum and type filter. The description lists the matchable fields but adds no meaning beyond the schema, such as how field='all' behaves or how page and limit interact.

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 states a specific verb and resource: searching Firefly III accounts. It also names the searchable fields, making the tool's purpose clear, though it does not explicitly differentiate itself from list_accounts or get_account.

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 implied by 'search' and the listed match fields, suggesting this tool is for finding accounts by identifier rather than browsing all accounts. However, it does not explicitly say when to use this instead of list_accounts or get_account.

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