Skip to main content
Glama
Sign In
kotlogramme

kotlogramme

by J0s3f
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Search contacts

telegram_search_contacts
Read-onlyIdempotent

Search saved contacts and Telegram's public directory by name or @username to locate matching contacts and directory entries.

Instructions

Searches the saved contacts and Telegram's public directory by name or @username.

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": {
      "query": "<query>"
    },
    "name": "telegram_search_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matches to return.
queryYesThe name or @username to look for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds real value by making explicit that results span both saved contacts and the public directory, which the openWorldHint only hints at. It says nothing about matching semantics (prefix vs substring), result ordering, or what happens when the two sources overlap.

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?

A single front-loaded sentence with zero filler; the dual-source scope is stated before the matching key, which is the right order for an agent scanning the definition.

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 two-parameter read-only lookup with full schema coverage, rich annotations, and no output schema, the description supplies the essential scope. Only secondary details (match type, ordering across the two result sets) are absent, which is acceptable at this complexity.

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%, so both query and limit are already documented in the schema, establishing the baseline of 3. The phrase 'by name or @username' loosely maps to the query parameter but adds no format, prefix-matching, or precedence details beyond what the schema states.

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?

States a specific verb ('Searches') and two concrete resources (saved contacts and Telegram's public directory) plus the matching key (name or @username). This is clearly distinguishable from a plain contact listing, though it does not name telegram_list_contacts as the non-search counterpart.

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?

The description implies when the tool is appropriate (fuzzy lookup by name or handle across two sources) but gives no explicit when-not guidance or pointer to alternatives such as telegram_list_contacts for enumerating saved contacts. Usage must be inferred from the scope wording alone.

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