Skip to main content
Glama

send_news

Sends rich news card messages with a title, description, link, and optional image to DingTalk group chats, enabling teams to share clickable updates and announcements.

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": {
      "title": "<title>",
      "description": "<description>",
      "url": "<url>"
    },
    "name": "send_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes点击后跳转的链接
titleYes图文消息标题
picUrlNo图片 URL(可选)
descriptionYes图文消息描述

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 exist, so the description carries the whole behavioral burden. Beyond 'sends a message', it discloses nothing about the destination group/webhook, permission or token requirements, external and irreversible side effects, rate limits, or what a success/failure response looks like.

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 well-formed sentence, front-loaded with the action and destination. Slight redundancy with the schema's own field list is the only waste.

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 four-parameter send tool with full schema coverage, the definition is minimally sufficient. It nonetheless omits where the message goes (no group identifier parameter exists) and what calling it returns or how failures surface.

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?

With 100% schema description coverage, the schema already documents all four fields, including that picUrl is optional. The description merely restates the same four field names and adds no format, length, or content guidance beyond the schema.

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 gives a concrete verb and resource: send a rich link card (图文消息) into a DingTalk group, and names the payload contents. This implicitly separates it from siblings like send_text and send_markdown, though it never names an alternative explicitly.

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 message-type label (图文消息) implies when this is the right choice over text, image, or template card, but the definition states no explicit when-to-use condition, no prerequisites, and no exclusions.

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