Skip to main content
Glama
Sign In
kotlogramme

kotlogramme

by J0s3f
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Show a member's admin rights

telegram_get_member_rights
Read-onlyIdempotent

Shows which admin rights a member of a group or channel holds and which they lack, so you can verify their access.

Instructions

Shows which admin rights a member of a group or channel holds and which they lack.

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": "<chat>",
      "user": "<user>"
    },
    "name": "telegram_get_member_rights"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYesThe chat: 'me' for Saved Messages, an @username, or a numeric chat id as listed by telegram_list_chats. Invite links are not accepted.
userYesThe person: an @username or a numeric user id as listed by telegram_list_members or telegram_list_contacts. Invite links and 'me' are not accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the result includes both granted and missing rights, which is useful output framing. It says nothing about permission requirements, behavior for non-admin callers, or errors for invalid chat/user.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is what leaves the gaps in guidance and behavior rather than being a structural flaw.

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 two-parameter read-only tool with full schema coverage and annotations, the description is minimally adequate. However, with no output schema, it should say more about what the returned rights structure looks like and should mention the admin-privilege requirement, both of which an agent needs to call it correctly and interpret failures.

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%, so the chat and user parameters are already fully documented with accepted formats and exclusions. The description adds no format, constraint, or interpretation beyond the schema; baseline 3 applies.

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

Purpose4/5

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

Clear specific verb-and-resource phrasing: 'shows which admin rights a member ... holds and which they lack'. It distinguishes itself from the name-only sibling telegram_list_members by indicating it returns rights, not rosters. It stops short of explicitly naming a sibling it replaces or complements.

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?

There is no when-to-use or when-not-to-use guidance and no alternative named. The description never states the prerequisite that the caller likely needs admin status in the group to query another member's rights, which is the single most important selection/usage condition for this tool.

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

Deploy Server

Other Tools