simple-support-system-mcp

by bitterdev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Approve ticket

approve_ticket

Idempotent

Approves a moderated support ticket so it becomes visible and editable via the API; an API key is required.

Instructions

Approve a moderated ticket so it becomes visible and editable through the API. Requires an API key.

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>"
    },
    "name": "approve_ticket"
  }
}

Input Schema

Name	Required	Description	Default
`ticketId`	Yes	Ticket to approve.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Oct 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations cover idempotency (idempotentHint=true) and open-world behavior, so the description is not the only source. It still adds real value by disclosing the postcondition (ticket becomes visible and editable) and the auth requirement (API key), though it doesn't say whether approval can be undone or who is permitted to approve.

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?

Two short sentences, no redundancy, with the effect of the operation front-loaded before the access requirement.

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 single-parameter approve operation with no output schema, the description covers the action, its consequence, and the auth prerequisite. It leaves minor gaps around reversibility and permission scope, but nothing required to invoke it correctly is missing.

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% and the single required parameter ticketId is fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 specific verb (approve) and resource (moderated ticket) plus the resulting state change, which clearly separates it from approve_comment and set_ticket_state. It does not explicitly name a sibling alternative, so it stops just short of the top mark.

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?

The phrase 'moderated ticket' implies the precondition for use, but there is no explicit when-to-use guidance, no statement of when approval is inappropriate, and no pointer to related tools such as set_ticket_state or approve_comment.

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