Skip to main content
Glama
Sign In
Telegram Bot API Docs MCP

Telegram Bot API Docs MCP

by yoxcito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_field

Retrieve detailed documentation for a method parameter or type field. Get field descriptions, types, and constraints directly from the official Telegram Bot API docs.

Instructions

Return documentation for a method parameter or type field.

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": {
      "owner_name": "<owner_name>",
      "field_name": "<field_name>"
    },
    "name": "get_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNo
field_nameYes
owner_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states what is returned, with no mention of side effects, authentication, or error conditions. Basic behavioral traits are missing.

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?

Single sentence with no waste. Information is front-loaded and efficient.

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

Completeness3/5

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

The tool has an output schema, so return values need not be detailed. However, with 3 parameters and no usage context, the description feels incomplete. It does not explain how to select parameters or typical usage.

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?

With 0% schema coverage, the description should clarify each parameter. It partially does by linking 'section' to methods/types, but does not explain owner_name or field_name beyond their names. Adds minimal meaning over schema.

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 clearly states that the tool returns documentation for a method parameter or type field. This is specific and distinguishes from siblings like get_method or get_type, though it could mention what the documentation includes.

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?

No guidance on when to use this tool over alternatives like get_method or get_type. The description does not provide any use case or exclusion criteria.

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