Lockstep Core

Overview Schema Source Related Servers Discussions Admin

update_ticket

DestructiveIdempotent

Modify ticket metadata such as priority, entity, or description, and append notes to maintain accurate project tracking and handoffs.

Instructions

Update ticket metadata and/or append a note.

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": {
      "params": "<params>"
    },
    "name": "update_ticket"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Sep 13, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description never explains what is overwritten (entity, priority, description are replacements) or that omitted fields are left untouched. 'Append a note' even suggests additive behavior that sits awkwardly beside destructiveHint=true, without resolving the difference.

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 efficient sentence that is front-loaded with the verb and resource. It is arguably too terse rather than bloated, but nothing in it is wasted.

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 destructive mutation touching five parameters, the description omits permissions, partial-update semantics, and the effect of null/default values. An output schema exists so return values are covered, but the mutation contract itself is under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool exposes five updatable fields (ticket_id, note, entity, priority, description), yet the description only alludes to 'metadata' and 'note'. With schema description coverage reported at 0%, the description fails to compensate by clarifying which fields are mutable, that priority is an enum, or that all fields except ticket_id are optional.

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?

States a clear verb (update) and resource (ticket), and names the two operation types: metadata changes and appending a note. It does not differentiate from siblings that also mutate tickets, such as tag_ticket, promote_ticket, or link_ticket_chain, so an agent must still infer the boundary from schemas.

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 exclusions, and no pointer to alternatives like tag_ticket or promote_ticket. The agent is left to guess whether updating a tag or priority belongs here or in a sibling tool.

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