Skip to main content
Glama

Update subtask

update_subtask
DestructiveIdempotent

Update an existing subtask in your organization. Only the fields you provide are changed (PATCH semantics). You can rename the subtask, update its description, change its status, billing type, and set an hour limit. 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": {
      "subtask_id": "<subtask_id>"
    },
    "name": "update_subtask"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew subtask name.
statusNoSubtask status. One of: Active, Inactive, Completed.
hour_limitNoHour limit for this subtask (0 = unlimited). Validated against the parent task's limit for the subtask's billing type.
subtask_idYesId of the subtask to update (required). Must be a subtask in your organization.
descriptionNoSubtask description.
billing_typeNoBilling type for this subtask. One of: TM, Fix, OVH. Must be allowed by the parent task.
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 flag destructiveHint=true, so the description earns credit for clarifying PATCH semantics — only supplied fields change, existing values are preserved — which softens and correctly frames that risk. It also surfaces the cross-field validation constraint on hour_limit/billing_type against the parent task. It does not cover permission requirements or what errors result from a billing_type the parent disallows.

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 sentences, front-loaded with the action and the PATCH caveat, with no filler. The id-discovery instruction is the last sentence where it belongs as an immediately actionable prerequisite.

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 a 7-parameter mutation with annotations, full schema coverage, and no output schema, the description covers semantics, field set, and id sourcing. What is missing is minor but real: whether fields can be cleared vs. left untouched, and how validation failures on cross-field constraints surface to the caller.

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%, including enum values and the hour_limit/billing_type validation note, so the schema already carries parameter meaning. The description's field list restates what the schema documents rather than adding new semantics, so 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 subtask") and scopes it to "in your organization." It also enumerates the mutable fields, so the agent knows exactly what surface it touches versus siblings like create_subtask, delete_subtask, or move_subtask.

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?

Gives a concrete prerequisite workflow: discover the id with find_billing_work and never ask the user for one. It does not spell out when to prefer update_task or move_subtask over this tool, so it falls short of full alternatives guidance, but the usage context is clear.

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