Skip to main content
Glama
Sign In
Claudegram

Claudegram

by sanjar-x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

archive_dialogs

Destructive

Archive multiple Telegram dialogs by providing chat IDs. This moves them out of the active list, keeping your chat view organized without losing data.

Instructions

Перенести N диалогов в архив.

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_ids": "<chat_ids>"
    },
    "name": "archive_dialogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctxNo
chat_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds no additional behavioral context such as reversibility, error behavior, or permission requirements. It merely restates the action without elaborating on consequences.

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

Conciseness3/5

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

The description is a single short sentence, which is front-loaded and free of fluff, but it is under-specified for the tool's complexity. It leaves out usage and parameter details, so it is not appropriately sized.

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

Completeness2/5

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

For a bulk, destructive operation, the description is too minimal. It does not mention the batch nature beyond 'N', implications of archiving, or return behavior, despite having an output schema and a destructive hint.

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?

Schema description coverage is 0% for 2 parameters. The description references 'N dialogs' but does not explicitly map this to the required chat_ids parameter, nor explain whether IDs can be integers or strings, or what the optional ctx parameter does.

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?

Description states 'Move N dialogs to archive', using a specific verb ('move') and resource ('dialogs'), with 'N' indicating a batch operation. This clearly distinguishes it from the singular sibling 'archive_dialog' and other dialog-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 like 'archive_dialog', 'unarchive_dialog', or 'delete_dialogs'. The description lacks any context about use cases or exclusions.

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