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

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Timeslip

freeagent_get_timeslip
Read-only

Retrieve a single timeslip by its ID to review or verify time entries in FreeAgent.

Instructions

Get a single timeslip by its 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": {
      "timeslip_id": "<timeslip_id>"
    },
    "name": "freeagent_get_timeslip"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeslip_idYesThe timeslip ID

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
Behavior2/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 nothing beyond that: no mention of behavior when the ID is not found, whether it is scoped to the authenticated user/company, or any auth requirements. It is essentially a restatement of the name, offering no extra behavioral context.

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 short sentence with the resource front-loaded and zero filler; nothing is redundant. It is appropriately sized for a one-parameter lookup, though it is so terse that it conveys nothing beyond the name and schema.

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 simple get-by-ID tool with a fully documented single parameter and read-only annotations, the essentials for calling it correctly are present. However, with no output schema, the agent has no description of what a timeslip record contains or how failures appear, leaving a modest gap.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents 'timeslip_id' including its pattern. The description's 'by its ID' merely echoes the schema and adds no semantic detail (e.g., where to obtain an ID). Baseline 3 applies when the schema does the heavy lifting.

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 ('Get') and resource ('a single timeslip'), and the qualifier 'single' implicitly separates it from the sibling freeagent_list_timeslips. It never names that sibling explicitly, so differentiation is implied rather than stated.

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: the phrase 'by its ID' suggests it should be called when an ID is already known, which is a reasonable inference against list_timeslips. There is no explicit when-to-use, when-not-to-use, or alternative named, so guidance is minimal but adequate for a trivial lookup tool.

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