Skip to main content
Glama
Sign In
kotlogramme

kotlogramme

by J0s3f
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Telegram account

telegram_whoami
Read-onlyIdempotent

Identify the signed-in Telegram account and verify the connection by returning its display name, numeric ID, username, and phone number. Call this first to confirm the server is connected.

Instructions

Shows which Telegram account this server is signed in as: display name, numeric id, username and phone number. Call it first to check that the connection works.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "telegram_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds value beyond them by disclosing the returned identity fields — notably that a phone number is exposed, which is relevant context for an agent deciding whether to surface the output — and by framing the call as a connectivity check. It stops short of noting failure modes (e.g. what an unauthenticated server returns).

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 sentences, both load-bearing: the first defines the output, the second defines when to reach for it. Front-loaded with the resource and zero filler.

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

Completeness5/5

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

For a parameterless read with no output schema, the description supplies the essential missing piece — the shape of the returned identity record — plus its intended first-call role. Nothing an agent needs to invoke it correctly is absent.

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

Parameters4/5

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

The tool takes no parameters and the schema is a closed empty object, so there is nothing to disambiguate. Baseline 4 applies; the description correctly implies no inputs are needed by describing it as a pure identity read.

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?

States a specific verb and resource ('Shows which Telegram account this server is signed in as') and enumerates exactly what comes back: display name, numeric id, username and phone number. An agent can distinguish this identity-check tool from all the list_*/search_* siblings without opening any schema.

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

Usage Guidelines4/5

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

Gives an explicit calling condition — 'Call it first to check that the connection works' — which tells the agent to use it as a connectivity/auth probe before other operations. It does not name explicit alternatives or when-not-to-use cases, but for a zero-argument identity probe there is little ambiguity to resolve.

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