Skip to main content
Glama

send_text

Sends plain-text messages to DingTalk group chats through a custom bot webhook for announcements and notifications.

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": {
      "content": "<content>"
    },
    "name": "send_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes消息文本内容

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 disclosure burden, and it provides almost none. It never says which group is targeted (there is no group parameter, so the destination must be preconfigured somewhere), whether credentials or a webhook are required, what happens on failure, or what the call returns. For a message-sending side-effect tool this is a meaningful gap.

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, front-loaded with the verb and the destination, with no filler. It is arguably too terse rather than padded, which is a completeness problem more than a structure problem.

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 one-parameter send tool this is minimally adequate: the agent knows what it does and what to pass. Missing are the destination group, delivery semantics, error behavior, and any return-value expectation, none of which is covered by an output schema or annotations.

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 at 100% schema coverage, so the baseline is 3. The description adds only the mild implication that 'content' is plain text with no markup or formatting, which is marginally beyond the schema but not substantive.

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 states a specific verb and resource — send a plain-text message to a DingTalk group — and the qualifier '纯文本' implicitly separates it from the format-specific siblings (send_markdown, send_image, send_template_card). It does not name any sibling explicitly, so it falls short of a 5, but an agent can still tell what this tool does.

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?

There is no explicit when-to-use or when-not-to-use statement. The 'plain text' wording hints that other message types belong to other tools, which is enough to imply usage, but the agent must infer the routing rather than being told.

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