telegram-bot-framework-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| framework_versionA | Which framework version this server's source corresponds to (NuGet version, git commit, date). |
| get_changesA | Public API diff of the TelegramBotBase library between two git refs (tags, branches, SHAs): added/removed types and added/removed public members, plus commit list. Only refs present in the clone work. |
| list_refsA | List tags and branches available for get_changes. |
| list_symbolsB | List C# types (class/interface/enum/struct/record) by name substring and optional kind. |
| get_symbolA | Show a type: doc comment, bases, public/protected members and file path. Use get_file for full source. |
| find_subclassesB | Find types that inherit from / implement |
| list_filesB | List repository files filtered by path prefix and extension. |
| get_fileC | Read a repository file (optionally a line range). |
| search_codeB | Case-insensitive substring search of the source; returns path:line: text. |
| list_doc_sectionsC | List README sections. |
| get_doc_sectionA | Get README section(s) by case-insensitive partial title, e.g. 'ButtonGrid'. |
| list_examplesB | List C# example and test-bot files. |
| list_guide_sectionsA | List sections of the curated how-to guide (decision tables, patterns, gotchas, checklist). |
| get_guide_sectionA | Read guide section(s) by number or partial title, e.g. '3.4', 'Navigation', 'Checklist'. |
| search_guideA | Search the how-to guide with a plain-English question or keywords (e.g. 'handle a button click', 'dispatcher'). Returns the best-matching sections, most relevant first, each with the key matching lines. Read a whole section with get_guide_section. |
| get_gotchasA | Known pitfalls as 'symptom -> cause & fix'. Pass words of your problem or error (e.g. 'spins forever', 'CallbackDataTooLongException'), or nothing for all. |
| askA | Best first call for any how-to question about building a bot with TelegramBotBase. Searches the guide, the known pitfalls, the type index and the README at once, and tells you which tool to call next. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| guide_resource | Curated how-to guide. |
| readme | Full README. |
TDQS
Scored across 17 tools
Most tools target clearly distinct facets (git refs, symbols, files, code search, README, examples, guide, gotchas), so an agent can usually pick correctly. The overlap is mild: `ask` deliberately subsumes `search_guide`, `get_gotchas`, `list_symbols` and README lookup, and `list_doc_sections`/`list_guide_sections` are two similar-looking pairs, but the docs explicitly frame `ask` as an orchestrator so the boundaries are explained.
Names follow a clear verb_noun convention (list_refs, get_symbol, find_subclasses, search_code, get_guide_section) across the whole set. Only two deviations stand out: the noun-only `framework_version` and the verb-only `ask`, which are minor and readable.
17 tools is on the heavy side for what is essentially a read-only repo/docs browser, and several doc-navigation tools (list_doc_sections/get_doc_section, list_guide_sections/get_guide_section, search_guide) could arguably be consolidated. Each still maps to a real facet of the repo, so it is heavy rather than bloated.
The surface covers versioning, API diffs, refs, symbol/subclass lookup, file listing and reading, code search, README, examples, the curated guide and pitfalls, and even an orchestrator entry point — a solid lifecycle for a documentation/reference server. Minor gaps remain: no full-text README search, no example-file search, and no way to enumerate all symbols in one call.