Skip to main content
Glama

send_markdown

Sends Markdown-formatted messages to DingTalk group chats, including titles, lists, and code blocks, so teams can share structured updates directly.

Instructions

向钉钉群发送 Markdown 格式消息,支持标题、列表、代码块等

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

Input Schema

NameRequiredDescriptionDefault
textYesMarkdown 格式的消息内容
titleYes消息标题

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 provided, so the description carries the full behavioral burden. It does disclose that the message goes to a group (an external, side-effecting send), but it says nothing about authentication/bot webhook requirements, rate limits, message size limits, or failure behavior — significant gaps for a messaging tool without annotations.

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 front-loaded sentence with the verb and format up front and no wasted preamble. The trailing '等' (etc.) is slightly vague but minor.

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 two-parameter send tool with full schema coverage and no output schema, the description covers the essentials of purpose and format. It falls short on DingTalk-specific operational constraints and what a successful or failed send looks like.

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?

Schema description coverage is 100% and both parameters are documented, so the baseline is 3. The description reinforces that text is Markdown with supported constructs, which adds modest clarification, but it adds nothing about title semantics, limits, or escaping.

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 uses a specific verb (send) and resource (Markdown message), and it scopes the action to a DingTalk group. The 'Markdown 格式' qualifier distinguishes it from siblings such as send_text and send_image, though it never names those siblings 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?

Usage is implied rather than stated: mentioning headings, lists, and code blocks suggests this tool is for rich-formatted messages, which hints at when to prefer it over send_text. There is no explicit when-to-use/when-not guidance or named alternative.

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