Skip to main content
Glama

Update task

update_task
DestructiveIdempotent

Update an existing task in your organization. Only the fields you provide are changed (PATCH semantics). You can rename the task, update its description, change its status, and set per-type hour limits. Discover ids with find_billing_work - never ask the user for an 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": {
      "task_id": "<task_id>"
    },
    "name": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew task name.
statusNoTask status. One of: Active, Inactive, Completed.
task_idYesId of the task to update (required). Must be a task in your organization.
descriptionNoTask description.
tm_hour_limitNoT&M (Time & Materials) hour limit for this task (0 = unlimited).
fix_hour_limitNoFixed-price hour limit for this task (0 = unlimited).
ovh_hour_limitNoOverhead hour limit for this task (0 = unlimited).
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true; the description adds the key non-obvious behavior that only supplied fields are changed (PATCH), which prevents accidental field clearing by an agent used to PUT-style updates. It does not explain the destructive surface (what is lost when a status or hour limit changes) or any permission requirements, which matters given destructiveHint=true.

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

Conciseness5/5

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

Three tight sentences with the mutation scope front-loaded, then the PATCH guarantee, then the id-discovery rule. No filler, no restatement of the title, and the most error-prone instruction (where to get ids) is placed last for emphasis.

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

Completeness4/5

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

For an 8-parameter mutation with no output schema, the description covers scope, partial-update semantics, mutable fields and id provenance, which is enough to call it correctly. Remaining gaps are permissions and what a destructive update actually affects, plus no hint about the returned object.

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 coverage is 100%, including the 0 = unlimited convention and enum values, so the schema does the heavy lifting. The description only groups the three hour-limit parameters as "per-type hour limits" rather than adding format, validation or edge-case meaning beyond the schema; baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("Update an existing task in your organization") and immediately scopes the mutation with PATCH semantics. It also enumerates the mutable surface (name, description, status, per-type hour limits), so an agent can distinguish it from create_task, delete_task and move_task without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes id discovery to find_billing_work with a strong instruction ("never ask the user for an id"), which is real when/how guidance for a sibling. It stops short of stating exclusions, e.g. that relocating a task across projects belongs to move_task, or that multi-task changes should go through a bulk tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources