Skip to main content
Glama
Sign In
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Tax Timeline

freeagent_get_tax_timeline
Read-only

Retrieves the company tax timeline so you can view upcoming tax deadlines and obligations in FreeAgent before they are due.

Instructions

Get the tax timeline for the company, showing upcoming tax deadlines and obligations.

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_tax_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds meaningful context about what the operation surfaces (upcoming deadlines and obligations) but says nothing about scope limits, whether an empty result means no configured tax timeline, or what the response looks like.

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?

A single front-loaded sentence that names the resource first and the returned content second; there is no padding or filler. Slight redundancy between "tax timeline" and "tax deadlines" keeps it from being maximally tight, but it is efficient overall.

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?

For a zero-parameter read-only tool this covers the essentials, and there is no output schema to defer to, so the description does some work in sketching the returned content. It stops short of describing the shape or granularity of the timeline (dates, obligation types, currency), which leaves a small but real gap.

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 is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a company-scoped call with no filtering options, which matches the empty 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?

States a specific verb and resource ("Get the tax timeline for the company") and sharpens it with what the payload contains ("upcoming tax deadlines and obligations"). This is not a sibling that could be confused with the financial report tools like get_profit_and_loss or get_balance_sheet, though the description never explicitly distinguishes itself from those accounting endpoints.

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 it should call this when it needs upcoming tax deadlines. There is no explicit when-to-use statement, no exclusion, and no pointer to a related sibling such as get_company or the P&L report, so the routing must be reasoned rather than read.

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