Obtain the complete scenario of an enrolled chat by passing its chat ID to retrieve the full interaction context.
Get the full scenario for an enrolled chat.
| Name | Required | Description | Default |
|---|---|---|---|
| chat_id | Yes |
Changes observed during successful MCP inspections.
v2.31.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The verb 'Get' clearly indicates a read-only operation with no side effects. Although no explicit statement about non-destructiveness is made, the name and description strongly imply it. With no annotations to rely on, the description carries the burden, and it is largely transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that directly conveys the tool's function without unnecessary detail or verbosity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simple getter nature and its context among sibling telegram_agent tools, the description provides enough information to understand its use. It does not specify the output format, but that is not essential for invoking the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The sole parameter chat_id is not described in the schema, but the tool description clarifies that it refers to an 'enrolled chat', giving it meaning and context. This is sufficient for an agent to infer its purpose.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and the resource ('full scenario') for a specific subject ('an enrolled chat'). It is unambiguous and distinct from related tools like telegram_agent_set_scenario.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is provided on when to use this tool versus alternatives such as telegram_agent_set_scenario or other telegram_agent_* tools. The description does not mention any conditions or alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.