Skip to main content
Glama
JonnadulaNagaSambaSivaRao

Customer Support MCP Server

create_ticket

Create a customer support ticket with customer name, email, subject, description, and priority to log and track issues.

Instructions

Create a new customer support ticket.

Args:
    customer_name: Customer's full name.
    customer_email: Customer's email address.
    subject: Short description of the issue.
    description: Detailed description of the problem.
    priority: Ticket priority: low, medium, high, or urgent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYes
priorityNomedium
descriptionYes
customer_nameYes
customer_emailYes
Behavior2/5

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

No annotations are provided, and the description carries full burden. It only states the action without disclosing side effects, required permissions, return behavior, or validation rules. This is a significant gap for a mutation tool.

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?

The description is brief, front-loaded with the purpose, and includes a structured Args list. Every part earns its place without unnecessary fluff.

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?

The description covers the purpose and parameters adequately, but without an output schema, it does not mention what the tool returns (e.g., ticket ID) or any post-creation behavior. This leaves a completeness gap.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates with an Args block that explains every parameter, including priority values. This adds clear meaning beyond the bare schema types.

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?

The description clearly states 'Create a new customer support ticket' with a specific verb and resource. It distinguishes from sibling tools (get_ticket, search_tickets, update_ticket) by focusing on creation.

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

Usage Guidelines4/5

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

The description clearly indicates its purpose, implying when to use it (creating tickets) versus alternatives (getting, searching, updating). It lacks explicit exclusions or when-not guidance, but the context is clear from the verb.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JonnadulaNagaSambaSivaRao/customer_support_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server