Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Get Firefly III System & User Info

get_system_info
Read-onlyIdempotent

Verify Firefly III connectivity and retrieve instance version, API version, and authenticated user profile.

Instructions

Verify connectivity to Firefly III and retrieve instance version, API version, and authenticated user profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_system_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the call read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral context by saying it verifies connectivity and returns instance version, API version, and authenticated user profile, which tells the agent what to expect beyond the safety profile.

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 a single front-loaded sentence with no redundant wording. Every clause contributes either the connectivity purpose or the specific return information.

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 parameterless read-only tool, the description covers purpose and expected return fields, while annotations cover safety behavior. It is nearly complete, though it could explicitly note that authentication is required to retrieve the user profile.

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 tool takes zero parameters, so there are no parameter semantics to explain. The baseline score for a parameterless schema applies, and the description does not introduce unnecessary parameter-like details.

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: verify connectivity and retrieve instance version, API version, and authenticated user profile from Firefly III. This clearly distinguishes it from sibling tools that operate on accounts and transactions, though it does not explicitly name those siblings as alternatives.

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

Usage Guidelines4/5

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

It gives clear usage context by framing the call as a connectivity check and a way to retrieve system and user metadata. It does not state when not to use it or name alternative tools, but for a unique zero-parameter informational endpoint, the implied usage is sufficiently clear.

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