Skip to main content
Glama
Sign In
tg

tg

by rodion1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

describe_media

Saves a one-line description of a photo or file to the Telegram archive, helping you label and retrieve media later.

Instructions

Сохраняет в архив короткое описание фото или файла (до 200 символов, одна строка).

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>",
      "id": "<id>",
      "text": "<text>"
    },
    "name": "describe_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
chatYes
textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the 200-character, single-line limit, but says nothing about what a write does to an existing description (overwrite vs append), what happens if the limit is exceeded, or what access to the chat is needed.

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?

A single compact sentence with the constraint front-loaded, no filler or repetition. It could only be improved by spending the same brevity on the chat/id meaning instead of having none.

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?

An output schema exists so return values need no explanation, but for a 3-required-parameter write tool with zero annotation and zero schema description coverage, the definition leaves the two targeting parameters and the write's side effects unexplained. That is not sufficient for confident invocation.

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% and the parameters are titled only Id, Chat, and Text. The description clarifies the text payload (short, one line, ≤200 chars) but leaves 'chat' (username, ID, or link?) and 'id' (which media identifier?) entirely undefined, which is the main risk for misinvocation.

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 concrete action and object: stores a short description of a photo or file, with an explicit size constraint (up to 200 characters, single line). It is clear enough to distinguish from siblings like ocr_photos, transcribe, or send_message, but it never explains the chat/id scoping, so the tool's exact target remains partly ambiguous.

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?

There is no statement of when to use this instead of alternatives such as send_message, ocr_photos, or transcribe, and no mention of prerequisites (must the media already be fetched or synced?). Usage must be inferred entirely from the name and one-line purpose.

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