Skip to main content
Glama
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez

freeagent_get_profit_and_loss

Read-only

Retrieve a FreeAgent profit and loss summary, optionally filtered by from and to dates, to analyze business income and expenses over a chosen period.

Instructions

Get the profit and loss summary from FreeAgent with optional date range filtering

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

Input Schema

NameRequiredDescriptionDefault
to_dateNoEnd date for the P&L report in YYYY-MM-DD format
from_dateNoStart date for the P&L report in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a safe, closed-world read. The description adds only that the date range is optional, and does not disclose what the default period is, whether the summary is aggregated by category, or the currency/accounting basis. That leaves a meaningful behavioral gap for a reporting tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no wasted words. Its brevity comes at the cost of the behavioral detail noted elsewhere, but the sentence itself is well-formed and efficient.

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?

This is a simple read tool with two optional, fully documented parameters and annotations covering safety, so little is required. Still, the description does not say what the summary contains or what period is used when no dates are supplied, which an agent would need in order to call it correctly.

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%, and both from_date and to_date are documented with the YYYY-MM-DD format in the schema. The description adds nothing beyond confirming that both are optional, so the baseline of 3 applies.

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: 'Get the profit and loss summary from FreeAgent'. This clearly separates it from other financial-report siblings such as get_balance_sheet and get_trial_balance. It does not explicitly name those alternatives, but the resource is unambiguous.

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?

It mentions 'optional date range filtering' but gives no guidance on when to use this report versus the balance sheet or trial balance, nor on what happens if the range is omitted. An agent must infer the default reporting period.

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

Deploy Server

Other Tools