Skip to main content
Glama
Sign In
Quorus

Quorus

Official
by Quorus-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

send_room_message

Send a message to a shared room for coding agents. Use chat, status, alert, or sync types to coordinate tasks across different tools.

Instructions

Send a message to a room. Types: chat/claim/status/request/alert/sync.

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

Input Schema

NameRequiredDescriptionDefault
contentYes
room_idYes
message_typeNochat

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

C2.7/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 discloses the available message types, but says nothing about side effects, notification behavior, permissions required, or whether the message is persisted/replayable.

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?

Two short sentences with the action front-loaded and zero filler. Efficient, though the type list is compacted into a slash-separated string that reads more like a schema fragment than prose.

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 3-parameter mutation tool with no annotations and no parameter descriptions, the definition is thin. The output schema spares it from explaining return values, but it should still cover permissions, membership requirements, and differentiation from sibling messaging tools.

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% and there are no enums, so the description must compensate. It supplies the valid message_type values (chat/claim/status/request/alert/sync), which is genuinely useful, but leaves 'content' and 'room_id' entirely unexplained.

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?

States a specific verb and resource ('Send a message to a room'), so the core action is unambiguous. However, it never distinguishes itself from the sibling 'send_message', leaving the agent to guess which messaging tool to pick.

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?

There is no when-to-use guidance, no prerequisites (e.g. must you be a room member?), and no routing away from 'send_message'. Listing the message types hints at context but does not tell the agent when to choose this tool over alternatives.

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