Skip to main content
Glama
doanhnd9989

DMTicket MCP Server

by doanhnd9989

delete_agent_in_team

Remove specified user IDs from a DMTicket team to manage agent membership.

Instructions

Remove an Agent from Team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idsYesIDs of users to be deleted from the team
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states only the basic action without disclosing effects like whether the agent is fully deleted or just removed from the team, reversibility, or prerequisites.

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?

A single sentence with no wasted words, but it lacks necessary details for a complete understanding; concise but not fully informative.

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?

For a simple tool with one parameter and no output schema, the description covers the basic purpose but omits behavioral context and side effects, leaving gaps.

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?

Only one parameter exists with 100% schema description coverage; the description does not add meaning beyond the schema, meeting baseline expectation.

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 'Remove an Agent from Team' uses a specific verb and resource, clearly distinguishing it from sibling tools like 'delete_agent_from_account' and 'delete_agent_in_inbox'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as 'update_agents_in_team' or 'delete_agent_from_account'; no context provided.

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