mcp-max-messenger

Get Admins

get_admins

Retrieve the list of administrators in a group chat, including user IDs, names, usernames, and permissions. Provide the chat ID to get admin details.

Instructions

Get the list of administrators in a group chat. Returns user_id, name, username, and permissions for each admin.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chat_id": "<chat_id>"
    },
    "name": "get_admins"
  }
}

Input Schema

Name	Required	Description	Default
`chat_id`	Yes	The chat_id of the group chat

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.2Jun 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return fields (user_id, name, username, permissions) but does not mention whether the bot must be an admin or what happens for non-group chats.

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?

Two concise sentences front-load the purpose and output. No redundant information.

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

Completeness4/5

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

For a simple read tool with one parameter and no output schema, the description is fairly complete, specifying the returned fields. However, it lacks details on error cases or permission requirements.

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% and the parameter description in the schema is adequate. The description adds no extra meaning beyond identifying the chat type as a group chat.

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 the verb 'Get' and the resource 'list of administrators in a group chat'. It distinguishes from sibling tools like set_admin and remove_admin which modify rather than read.

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

Usage Guidelines3/5

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

No explicit when to use or when not to use this tool. While reading the admin list is implied, there is no mention of alternatives or prerequisites like requiring bot admin rights.

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