Skip to main content
Glama

send_template_card

Send formatted template card messages to DingTalk group chats with Markdown content and optional link buttons, enabling structured announcements and updates.

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>",
      "markdownContent": "<markdownContent>"
    },
    "name": "send_template_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes卡片标题
singleUrlNo底部按钮跳转链接(可选)
singleTitleNo底部按钮文字(可选)
markdownContentYes卡片正文(Markdown 格式)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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, and it discloses almost nothing: no mention of the send being an outbound side effect to a live group, no permissions or robot/webhook setup requirements, no rate limits, and no note on failure behavior. Most notably the description says the message goes to a 钉钉群 while the schema contains no group or target parameter, leaving it unexplained how the destination is determined.

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 short sentence with the resource and capability front-loaded and no filler. It is efficient, though the same brevity is what leaves the behavioral and targeting gaps unaddressed.

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?

For a messaging tool with an external side effect, no annotations, and no output schema, one sentence is not enough: nothing is said about the implicit destination group, delivery result, or error/retry behavior. The schema covers the four inputs, but the description leaves the agent without an operational model of the call.

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% — title, markdownContent, singleUrl and singleTitle all carry inline Chinese descriptions — so the schema already does the parameter work. The description adds only "支持丰富的卡片布局", which hints that markdownContent is rendered as a layout but gives no extra meaning on formats, limits, or how singleTitle pairs with singleUrl.

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?

"向钉钉群发送模板卡片消息" gives a specific verb (发送) plus a specific resource (模板卡片消息) and target (钉钉群), which cleanly separates it from siblings send_text / send_markdown / send_image / send_news. It stops short of an explicit contrast with those siblings, but the resource noun is distinctive enough for an agent to route correctly.

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 clause "支持丰富的卡片布局" only implies when this tool is preferable to send_markdown or send_text (e.g., when a rich layout, title plus bottom button, is wanted). There is no explicit when-to-use rule, no exclusions, and no mention of prerequisites such as a group robot being configured, so the agent must infer the selection criteria.

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