Skip to main content
Glama
doanhnd9989

DMTicket MCP Server

by doanhnd9989

update_conversation

Update the priority and SLA policy of a conversation to manage response times effectively.

Instructions

Update Conversation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priorityNoThe priority of the conversation
sla_policy_idNoThe ID of the SLA policy (Available only in Enterprise edition)
Behavior1/5

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

No annotations are provided, so the description must disclose behavior. It only says 'Update', which is vague. It does not mention side effects, permissions, or what happens to existing data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While short, the description is under-specified. It does not provide enough information, making it not truly concise—just insufficient.

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

Completeness1/5

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

Given the large number of sibling tools and the lack of output schema, the description is completely inadequate. It fails to explain what the tool does beyond the name.

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% (both params have descriptions). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update Conversation' is a tautology of the tool name. It does not specify what aspect of the conversation is updated or provide any distinguishing details from sibling tools.

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

Usage Guidelines1/5

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

No usage guidelines are given. The description does not indicate when to use this tool versus alternatives like 'toggle_status_of_a_conversation' or 'update_custom_attributes_of_a_conversation'.

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/doanhnd9989/dmticket-mcp'

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