Skip to main content
Glama
Sign In
Claudegram

Claudegram

by sanjar-x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_dialog_filter

Destructive

Delete a custom Telegram chat folder using its filter ID. Cleans up your dialog organization without affecting messages.

Instructions

Удалить кастомную папку диалогов.

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": {
      "filter_id": "<filter_id>"
    },
    "name": "delete_dialog_filter"
  }
}

Input Schema

NameRequiredDescriptionDefault
filter_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior2/5

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

The annotations already indicate destructiveHint=true, so the agent knows this is a destructive operation. The description adds no extra behavioral context beyond the literal meaning of 'delete'—it does not mention irreversibility, the effect on chats within the folder, or any prerequisites. Thus, no additional value over annotations.

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, concise sentence that directly conveys the tool's core purpose. No filler, front-loaded and unambiguous.

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 is simple (one parameter, output schema exists, annotations provide safety), so the minimal description is adequate. However, it leaves gaps such as the need to obtain filter_id from a list operation and the fact that only the folder is deleted, not its contents. It is minimally viable but lacks richer context.

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?

The schema has one parameter, filter_id, with no description (0% coverage). The description does not explain what filter_id refers to or how to obtain it. The parameter name is self-explanatory given the tool name, but the description adds no semantic value beyond the schema.

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 'Удалить кастомную папку диалогов' clearly states the action (delete) and the resource (custom dialog folder). It distinguishes itself from sibling tools like get_dialog_filters and create_dialog_filter by specifying the delete operation on a filter.

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?

The usage context is implied: if you need to remove a custom folder, this is the tool. However, it does not explicitly mention alternatives or exclusions (e.g., use delete_dialog for individual chats), nor does it advise obtaining filter_id from get_dialog_filters first.

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