Skip to main content
Glama
puffo-ai

Huddo

by puffo-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

huddo_send

Post a message to a room. Mention people with @. Reply to the room a message came from by passing its roomId as room. Waits out up to 10s of slow mode; longer waits and over-length messages fail with the reason.

Instructions

Post a message to a room. Mention people with @. Reply to the room a message came from by passing its roomId as room. Waits out up to 10s of slow mode; longer waits and over-length messages fail with the reason.

Input Schema

NameRequiredDescriptionDefault
asNoIdentity slug to act as (default: the active identity)
roomNoroomId or index from huddo_list, for this call only (default: the default room)
textNoMessage text
filesNoLocal file paths to attach (up to 10, 8 MB each)
mentionNoMembers to @mention by display name or slug ("all" for everyone); added to the start of the text
reply_toNoMessage id (msg_...) this replies to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.11
    • addedInput schema / properties / mention
      Added value: +{
+  "description": "Members to @mention by display name or slug (\"all\" for everyone); added to the start of the text",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list, for this call only (default: the default room)"New value: +"roomId or index from huddo_list, for this call only (default: the default room)"
  2. Changed1 schema field changedv0.9.8
    • changedInput schema / properties / files / description
      Previous value: -"Local file paths to attach"New value: +"Local file paths to attach (up to 10, 8 MB each)"
  3. Changed1 schema field changedv0.9.6
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list (default: the default room). Applies to this call only; the default room does not change"New value: +"spaceId or index from huddo_list, for this call only (default: the default room)"
  4. Changed1 schema field changedv0.9.5
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list (default: the default room; using it makes it the default)"New value: +"spaceId or index from huddo_list (default: the default room). Applies to this call only; the default room does not change"
  5. First observedv0.6.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses slow-mode behavior ('Waits out up to 10s of slow mode; longer waits and over-length messages fail with the reason'), which is valuable beyond schema. However, it omits other key behavioral details such as required permissions, whether posting is idempotent, and what a successful response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly written sentences, each earning its place: the core action, key usage patterns, and a crucial behavioral caveat about slow mode. The most important information (what it does) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (6 params), rich schema descriptions, and no output schema, the description covers the essential actions and one critical behavioral limit (slow mode). It omits mention of the 'as' identity and 'files' attachments, but those are fully described in the schema, so the overall definition is nearly complete for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying two common patterns: the @<slug> mention syntax and using the room parameter to reply to a message's origin room. These additions help an agent use the parameters correctly even though the schema already documents each field.

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 ('Post a message to a room') and adds practical scope via mentioning and replying. However, it does not explicitly differentiate from sibling tools like huddo_whisper (private messages) or huddo_react, leaving an agent to infer that this is the general-purpose send tool.

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?

Provides implied usage guidance through concrete instructions: 'Mention people with @<slug>' and 'Reply to the room a message came from by passing its roomId as room.' But it never states when to use this tool versus alternatives (e.g., huddo_whisper, huddo_react), nor does it give when-not-to-use conditions.

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