Skip to main content
Glama
Sign In
HomarUScc

HomarUScc

by kcdjmaxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

telegram_send_photo

Send a photo from a local file path to a Telegram chat by specifying the chat ID and file path. Optionally include a caption for context.

Instructions

Send a photo to a Telegram chat from a local file path.

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": {
      "chatId": "<chatId>",
      "filePath": "<filePath>"
    },
    "name": "telegram_send_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIdYesTelegram chat ID
captionNoOptional caption for the photo
filePathYesAbsolute path to the image file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description only states the action without disclosing any behavioral details such as side effects (message sent to chat), required permissions (e.g., bot token), error handling, or return values. This leaves the agent reliant on guesswork.

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 with the essential action. It is appropriately sized and avoids unnecessary detail.

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 with full parameter coverage, but the description lacks context about expected return values or failure modes. Since there is no output schema, the agent has no idea what the tool returns after sending. It is minimally complete for a basic operation but could benefit from mentioning confirmation behavior.

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?

The input schema has 100% coverage, documenting chatId, filePath, and caption clearly. The description adds the phrase 'from a local file path' which clarifies filePath but does not substantially enhance parameter understanding beyond what the schema provides.

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 tool's function: 'Send a photo to a Telegram chat from a local file path.' This distinguishes it from sibling tools like telegram_send (likely for text), telegram_react, and telegram_typing by specifying the exact action and resource.

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?

Usage context is implied (when you need to send a photo from a local file), but there is no explicit guidance on when to choose this over telegram_send or other Telegram tools. No alternative tools are mentioned, so the guidance remains implicit.

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