mcp-starter

Draft a support ticket

draft_support_ticket

Read-onlyIdempotent

Validate support ticket details and generate a draft for human review without sending or saving anything.

Instructions

Validate a support ticket and return a draft for a human to review.

Nothing is sent or saved. Swap the body for a call to your ticketing system.

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": {
      "ticket": "<ticket>"
    },
    "name": "draft_support_ticket"
  }
}

Input Schema

Name	Required	Description	Default
`ticket`	Yes

Output Schema

Name	Required	Description	Default
`subject`	Yes
`summary`	Yes
`draft_id`	Yes
`priority`	Yes
`related_docs`	Yes
`customer_email`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false. The description reinforces that safety profile with "Nothing is sent or saved." That is useful confirmation, but it largely restates what annotations already say. It adds little beyond that, such as what validation rules apply or how the draft is shaped.

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?

It is three short sentences with no wasted words, and the core purpose comes first. The side-effect disclaimer follows immediately. It is appropriately sized for a simple draft tool.

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?

An output schema exists, so the description need not explain the return shape. Annotations cover the safety profile. Still missing is what "validate" means in practice and what a caller should expect from the human-review step. For a tool whose whole value is producing a reviewable draft, that omission leaves the description only minimally sufficient.

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 description says nothing about the single ticket parameter or its nested fields. The schema does carry constraints, enums, and two field-level descriptions, but overall schema description coverage is reported as 0%. With that gap, the description should compensate, and it does not.

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 states a specific verb pair and resource: "Validate a support ticket and return a draft." That is far more precise than the title alone, and it is clearly distinct from the only sibling, search_docs. It stops short of naming that sibling as an alternative, so it is not 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?

It implies the use case: prepare a ticket for human review before sending. The phrase "Swap the body for a call to your ticketing system" hints that this tool is a stand-in for a real submission step. There is no explicit when-to-use or when-not-to-use guidance, and no prerequisites are stated.

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

Deploy Server