Skip to main content
Glama
doanhnd9989

DMTicket MCP Server

by doanhnd9989

add_new_agent_to_team

Add one or more agents to a team by providing their user IDs.

Instructions

Add a New Agent

Input Schema

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

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

No annotations provided. The description does not disclose behavioral traits such as whether the agent already exists, permission requirements, or side effects of adding to a team.

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?

Extremely short (4 words) but lacks critical context. It is not appropriately sized; it sacrifices clarity for brevity.

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

Completeness2/5

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

Given no annotations and no output schema, the description should provide more. It fails to explain what 'New Agent' means or that it refers to adding a user to a team. Incomplete for the tool's complexity.

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 coverage is 100% with a clear description for user_ids. The description adds no additional meaning beyond the schema, meeting baseline expectations.

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

Purpose2/5

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

Description is 'Add a New Agent', which is vague. The tool name includes 'to_team' but the description omits this, failing to specify that the agent is being added to a team. This could be confused with adding an agent to an account or 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 vs siblings like 'add_new_agent_to_account' or 'add_new_agent_to_inbox'. No exclusions or 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