Skip to main content
Glama
doanhnd9989

DMTicket MCP Server

by doanhnd9989

get_account_reporting_events

Retrieve account reporting events filtered by event name, timestamp range, user ID, or inbox ID to monitor key metrics like first response, resolution, and reply time.

Instructions

Account Reporting Events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter events by event name (e.g., first_response, resolution, reply_time)
sinceNoThe timestamp from where events should start (Unix timestamp in seconds)
untilNoThe timestamp from where events should stop (Unix timestamp in seconds)
user_idNoFilter events by user/agent ID
inbox_idNoFilter events by inbox ID
Behavior1/5

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

No annotations are provided, and the description gives no behavioral information. It does not disclose whether the tool is read-only, destructive, requires authentication, or any side effects, leaving the agent blind.

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?

The description is extremely short—a single fragment. While it is not verbose, it is under-specified and fails to convey essential information, making it more of an omission than concise.

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 5 parameters, no output schema, no annotations, and a sibling tool, the description is woefully incomplete. It does not explain what reporting events are, return format, limits, or filtering context.

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 descriptions for all 5 parameters. The tool description adds no extra 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.

Purpose2/5

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

Description is a tautology of the name, stating 'Account Reporting Events' without specifying an action. It does not clarify that the tool retrieves or lists events, nor does it distinguish from the sibling 'get_conversation_reporting_events'.

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. alternatives. The sibling tool 'get_conversation_reporting_events' exists but is not mentioned, and there is no context on prerequisites or scenarios.

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