Skip to main content
Glama

send_image

Sends an image to a DingTalk group chat through a bot webhook using a publicly accessible image URL, so teams can share visual updates directly in group conversations.

Instructions

向钉钉群发送图片消息(通过图片 URL)

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": {
      "imageUrl": "<imageUrl>"
    },
    "name": "send_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageUrlYes图片的 URL 地址,需公网可访问

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about authentication, how the target group is determined (the sole parameter is imageUrl — no group or chat identifier), delivery timing, failure modes, or rate limits. Only the high-level 'send to a DingTalk group' behavior is conveyed, which is a significant gap for a write operation with zero annotation coverage.

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?

One short sentence that front-loads the action and channel with no wasted words. It is arguably over-terse, but nothing is redundant or buried.

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 simple one-parameter send operation the purpose is adequately covered, but with no annotations and no output schema, the definition should clarify how the destination group is resolved and what happens on failure. Those omissions leave an agent unable to predict the call's effect beyond the obvious.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that imageUrl must be publicly accessible — a detail the description omits. The description's '(via image URL)' merely restates the schema rather than adding format, size, or constraint details.

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?

States a specific verb (send) and resource (image message) plus the channel (DingTalk group) and the mechanism (via image URL), which clearly distinguishes it from siblings like send_text or send_markdown. It stops short of explicitly naming or contrasting those siblings, but the resource itself makes the distinction obvious.

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 is only implied: send this when the content is an image rather than text/markdown/card. There is no explicit when-to-use statement, no preconditions, and no mention of alternatives such as send_text for non-image content.

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