Skip to main content
Glama

Texts of the Telegram bot's profile

dosai_update_telegram_profile
Destructive

Set what a client sees before writing to the project's Telegram bot: description (the text on the empty chat screen, up to 512 characters) and short_description (in the bot's profile, up to 120). Shown to every client, confirm the text with the owner. Requires admin or owner role.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_update_telegram_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
descriptionNo
short_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare write access (readOnlyHint=false, destructiveHint=true, openWorldHint=true); the description adds the consequence an agent actually needs, that the text is shown to every client before they write to the bot, plus the role requirement and the need for owner confirmation. That meaningfully justifies the destructive flag. It does not state whether omitted fields are preserved or cleared, leaving the exact mutation footprint ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with no filler, front-loaded on what the tool sets before moving to visibility, approval, and permissions. The embedded parentheticals make the middle clause slightly harder to scan, but nothing is wasted.

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?

For a three-parameter, no-output-schema mutation tool the description covers both optional fields, visibility, and role requirements well. The critical gap is update semantics: with destructiveHint=true and all fields optional, an agent cannot know whether sending only description clears short_description. That is the single fact most needed before invoking a destructive write.

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 description coverage is 33% (only project_id is documented), so the description must carry the other two fields; it does so usefully by explaining where each appears in Telegram (empty chat screen versus bot profile). The character limits repeat the schema's maxLength values rather than adding new information. The partial-update semantics for a request where only project_id is required remain unaddressed.

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 names a specific verb (set) and resource (the Telegram bot's profile text) and explicitly enumerates the two settable fields, description and short_description, with limits. An agent can tell this apart from profile-reading or bot-connection tools. It stops short of naming the nearest sibling (e.g. dosai_update_bot_settings or dosai_compose_bot_description) to draw a hard boundary.

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?

It supplies prerequisites (admin or owner role) and an approval instruction (confirm the text with the owner), which is real guidance about how to proceed. However, it gives no when-to-use versus alternatives guidance, so an agent cannot tell from the text whether it should call this or a sibling such as dosai_compose_bot_description to author the text.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources