Skip to main content
Glama

net_ticket_create

Create an operations ticket from an alarm or fault description and return the ticket number, SLA deadline, and initial status.

Instructions

根据告警/故障描述创建运维工单,输出工单号、SLA 时限与初始状态。

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": {
      "title": "<title>",
      "severity": "<severity>"
    },
    "name": "net_ticket_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes工单标题
sourceNo来源,如 alarm / inspection / manual
severityYes严重级别

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the useful behavioural facts that the call is a creating mutation and that it returns a ticket number, SLA deadline and initial status, but it says nothing about required permissions, idempotency or duplicate-ticket behaviour, or whether severity drives the SLA.

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 front-loaded sentence with no filler: purpose first, inputs and outputs second. Every clause carries information an agent needs.

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

Completeness3/5

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

Because there is no output schema, the description's mention of ticket number, SLA deadline and initial status is valuable and covers the return. However, for a mutation tool with zero annotations and no output schema, the absence of permission, idempotency and side-effect notes leaves a real gap.

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% (title, source, severity all documented with an enum on severity), so the schema does the heavy lifting. The description adds only that inputs describe an alarm/fault and implies severity feeds the SLA, without explaining P1/P2/P3 semantics or valid source values beyond the schema.

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 names a specific verb and resource (create an operations ticket) and states the input basis (alarm/fault description), which clearly separates it from the sibling net_ticket_update. It does not explicitly name or contrast with that sibling, so it falls short of a 5.

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: 'based on an alarm/fault description' suggests it should be used when an alarm or fault has been identified, but there is no explicit when-to-use, when-not-to-use, or pointer to net_ticket_update for modifying existing tickets. The agent must infer the routing.

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