Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by jgalea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_user

Fetch Telegram user profile information using a user ID. Get essential details to identify users and manage chat interactions.

Instructions

Get user profile info

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": {
      "user_id": "<user_id>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.7/5.0
Behavior2/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 for behavioral transparency. The verb 'Get' implies a read-only operation, but the description does not disclose authentication requirements, possible errors for invalid user IDs, or whether any side effects exist. It adds little beyond the purpose statement.

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?

The description is concise and front-loaded with the action, containing no filler words. However, it is so terse that it omits necessary context, so while efficient, it is not maximally helpful as a standalone definition.

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?

For a one-parameter getter with no output schema and no annotations, this description is minimally usable but incomplete. It does not clarify what 'profile info' includes, how user_id should be interpreted, or when to choose this tool over sibling retrieval tools, leaving key selection and behavior gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the user_id parameter. The parameter name and type are somewhat self-explanatory, but the description does not clarify whether a string value is a username, phone number, or other identifier, so it fails to compensate for the missing schema documentation.

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?

The description states a specific verb ('Get') and resource ('user profile info'), clearly indicating the operation is retrieving a user's profile. However, it does not differentiate from sibling tools like get_contact or get_me, which could overlap in purpose.

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 guidance about when to use get_user versus alternatives such as get_contact, get_me, or get_status. The description provides no context on selection criteria, prerequisites, or exclusions.

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