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

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Timeslip

freeagent_update_timeslip
Destructive

Update an existing FreeAgent timeslip by changing its task, hours, comment, or date using the timeslip ID. Use it to correct or adjust recorded time entries.

Instructions

Update an existing timeslip in FreeAgent.

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

Input Schema

NameRequiredDescriptionDefault
taskNoTask URL
hoursNoNumber of hours as a decimal string
commentNoComment for the timeslip
dated_onNoDate for the timeslip (YYYY-MM-DD)
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

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is structured data, and the description adds nothing beyond it. Critically, it does not say whether omitted fields are left untouched or cleared — a material question for a call flagged destructive — nor whether the update is reversible or requires auth scopes.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, but its brevity comes from under-specification rather than economy — there is no second sentence carrying the update semantics that the schema and annotations leave implicit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation flagged destructive with no output schema, the description should at minimum cover partial-update semantics and what the call returns. As written it leaves the agent guessing about those behaviors, which is a significant gap for a write operation.

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 every parameter including the required timeslip_id and the task/hours/dated_on fields is already documented in the schema. The description adds no extra meaning such as date format caveats, task URL expectations, or hours precision, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update an existing timeslip" gives a clear verb and resource, and the word "existing" distinguishes it from freeagent_create_timeslip. However, it never says which fields can change or how it differs from siblings like freeagent_delete_timeslip or freeagent_start_timer, so the agent must open the schema to learn anything concrete.

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?

There is no when-to-use guidance, no prerequisite (e.g. the timeslip must exist, required permissions), and no named alternative. The agent gets no signal about preferring this over delete/create or over listing timeslips first to obtain a valid timeslip_id.

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