Skip to main content
Glama

net_ticket_update

Transitions network tickets through defined states (OPEN→ACK→FIXED→CLOSED) and returns INVALID_TRANSITION for disallowed moves.

Instructions

按状态机推进工单:OPEN→ACK→FIXED→CLOSED,非法流转返回 INVALID_TRANSITION。

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": {
      "ticketId": "<ticketId>",
      "to": "<to>"
    },
    "name": "net_ticket_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes目标状态
ticketIdYes工单号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does usefully disclose the validation rule set (legal transitions) and the failure signal INVALID_TRANSITION, but says nothing about required permissions, whether CLOSED is terminal/irreversible, or concurrency effects.

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?

A single sentence that front-loads the state machine and ends with the error behavior; nothing is wasted and no clause needs rereading.

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 two-parameter mutation tool this covers the essential contract: legal states, ordering, and failure outcome. The remaining gap is the success return value, which no output schema documents, plus permission prerequisites.

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

Parameters4/5

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

Schema coverage is 100% and both parameters already carry descriptions, so the baseline is 3. The description earns an extra point by giving the transition chain, which supplies real meaning for the `to` enum — showing that ACK is only valid from OPEN, FIXED from ACK, and so on.

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 (advance/push forward) plus the resource (ticket) and enumerates the entire state machine OPEN→ACK→FIXED→CLOSED. An agent can tell this is the state-transition tool and not net_ticket_create just from the sentence.

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

Usage Guidelines3/5

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

Usage is only implied: call it when a ticket must move to a new state, and the enumerated chain quietly conveys that only forward transitions apply. There is no explicit when-to-use/when-not guidance or reference to any alternative tool.

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