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

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Task

freeagent_update_task
Destructive

Update an existing FreeAgent task's name, status, billable flag, billing rate, or billing period using its task ID.

Instructions

Update an existing task 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": {
      "task_id": "<task_id>"
    },
    "name": "freeagent_update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the task
statusNoTask status: Active, Completed, or Hidden
task_idYesThe ID of the task to update
is_billableNoWhether the task is billable
billing_rateNoBilling rate for the task
billing_periodNoBilling period: hour, day, week, month, or year

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.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — it never warns that the operation is destructive, whether omitted fields are preserved or cleared, or what happens on an invalid task_id, which is exactly the value the prose should supply.

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?

One short, front-loaded sentence with no filler or repetition. It is efficient, though its brevity borders on under-specification rather than true concision.

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 six-parameter mutation flagged as destructive with no output schema, the description leaves out partial-update semantics, side effects, and error behavior. What an agent needs to call it safely is missing, even though the schema documents the individual fields.

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%, with all six parameters documented, including two enums, so the schema carries the semantics. The description adds no extra meaning such as whether billing_rate requires is_billable or how billing_period interacts with billing_rate; baseline 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 (update) and resource (task) in a named system, so an agent knows exactly what operation it performs. It does not, however, differentiate itself from the sibling freeagent_create_task, freeagent_delete_task, or freeagent_get_task beyond the verb itself.

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 guidance on when to use this tool versus the other task tools, no mention of prerequisites (e.g. the task must exist, task_id required), and no statement about whether it is a full replacement or a partial update. Usage is only inferable from the verb.

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