Skip to main content
Glama
Sign In
mailnotmilk

mailnotmilk

by jrb00013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

chat_say

Post a message into a chat room using its chat ID. Specify the text and optionally the sender or recipient to relay it.

Instructions

Post a message into a chat room (by chat id).

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": {
      "chat_id": "<chat_id>",
      "text": "<text>"
    },
    "name": "chat_say"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
textYes
chat_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

C2.5/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it reveals nothing beyond the obvious 'post' action. It does not mention side effects, permissions, reversibility, return format, or any other behavioral characteristics, making it impossible for the agent to anticipate the tool's impact.

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?

The description is a single, concise sentence with no fluff or redundant information. It is front-loaded with the verb and object, but it is too terse to serve as a complete guide, though conciseness itself is not a fault.

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?

Given the tool's relative simplicity (4 parameters, no output schema), the description is still incomplete. It omits guidance on the optional parameters, any return value, and usage context, leaving significant gaps for an agent attempting to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It implicitly explains chat_id ('by chat id') and text ('message'), but the optional 'to' and 'from' parameters are completely unaddressed, leaving the agent with only names to guess their meaning.

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 clearly states the action ('Post a message') and the target resource ('a chat room'), with the key parameter ('by chat id'). It is unambiguous, though it does not distinguish from sibling tools like post_message or browser_send_message, which could overlap in function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives. It only states what it does; there is no mention of context, prerequisites, or exclusions, leaving the agent without a basis for tool selection among several messaging-related tools.

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

Deploy Server

Other Tools