Skip to main content
Glama
Sign In
Claudegram

Claudegram

by sanjar-x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

edit_chat_about

Set or update the about/bio description for any Telegram chat by providing the chat identifier and new text.

Instructions

Установить описание чата (about/bio).

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": {
      "chat": "<chat>",
      "about": "<about>"
    },
    "name": "edit_chat_about"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
aboutYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive behavior. The description adds no further behavioral traits such as permission requirements, side effects, or scope of change, leaving the tool's behavior minimally disclosed.

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?

The description is a single, direct sentence that is front-loaded and contains no wasted words. It is appropriately concise for a simple setter tool.

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 description is minimally viable given the presence of annotations and an output schema, but it lacks context about when to use the tool, required permissions, or limitations relative to sibling tools. More contextual detail would improve completeness.

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 description coverage, the description must compensate for parameter meaning. It clarifies that 'about' refers to the chat's about/bio, but it leaves 'chat' ambiguous—likely an identifier, but no format or acquisition method is provided. This is insufficient for full parameter semantics.

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 'Set chat description (about/bio)' clearly states the action (set) and the target resource (chat description), distinguishing it from sibling tools like edit_chat_title and edit_chat_photo.

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 is provided on when to use this tool versus alternatives such as edit_chat_title, update_profile, or other chat-editing tools. It also omits prerequisites like required permissions or applicable chat types.

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