Skip to main content
Glama
Sign In
kotlogramme

kotlogramme

by J0s3f
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

List login sessions

telegram_list_sessions
Read-onlyIdempotent

Lists all devices logged in to your Telegram account with device, app, IP, country, and start time, marking the session used by the server so you can audit or revoke access.

Instructions

Lists the devices logged in to the user's account with their 'hash', device, app, IP address, country and when they started. The current one, which this server uses, is marked.

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_list_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is supplied elsewhere. The description earns credit for disclosing the shape of the response (which fields come back, including a 'hash' identifier) and for flagging that the server's own session is marked, which is operational context an agent could not infer from the schema.

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 short sentences, front-loaded with the core action and then the returned fields, ending on the one non-obvious caveat. There is no filler and nothing repeated from the title.

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 parameterless list call whose annotations already cover the safety profile, the description is sufficient to call it correctly. A small gap remains: it never says what the 'hash' is for or what the caller should do with it, which matters because there is no output schema to explain the identifier's role.

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 input schema is an empty closed object at 100% coverage, so there is nothing for the description to disambiguate. The baseline for a zero-parameter tool applies.

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 opens with a specific verb and resource ('Lists the devices logged in to the user's account') and then enumerates the returned fields (hash, device, app, IP, country, start time). No sibling tool in the catalog lists sessions, so there is no ambiguity to resolve, and the 'current one ... is marked' detail pins down the scope precisely.

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?

Usage is implied rather than stated: it is obviously a read-only inventory call, and the note that the current session is flagged hints at why you'd call it, but there is no explicit 'use this when' guidance and no warning that the session this server runs on should not be acted upon. With zero parameters there are no alternatives to choose between, which keeps this from being a real defect.

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