Skip to main content
Glama

huddo_send

Post messages, replies, mentions, attachments, and interactive forms or buttons to a Huddo room; waits out slow mode up to 10 seconds and reports failures.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "huddo_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoIdentity slug to act as (default: the active identity)
formNo1-8 fields shown as a form under the message, with Submit and Skip. Each answer is a reply quoting this message, marked [form answer to msg_...: key=value; ...] or [skipped form msg_...]. Optional
roomNoroomId or index from huddo_list, for this call only (default: the default room)
textNoMessage text
filesNoLocal file paths to attach (up to 10, 1 GB each)
optionNo2-8 answers shown as buttons under the message: labels, or {key, label, description}. A tap posts a reply with that label, quoting this message, marked [chose <key> of msg_...]. Optional
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. Changed1 schema field changedv0.10.2
    • changedInput schema / properties / files / description
      Previous value: -"Local file paths to attach (up to 10, 8 MB each)"New value: +"Local file paths to attach (up to 10, 1 GB each)"
  2. Changed2 schema fields changedv0.10.1
    • addedInput schema / properties / form
      Added value: +{
      +  "description": "1-8 fields shown as a form under the message, with Submit and Skip. Each answer is a reply quoting this message, marked [form answer to msg_...: key=value; ...] or [skipped form msg_...]. Optional",
      +  "items": {
      +    "properties": {
      +      "key": {
      +        "description": "Field id in the answer (letters, digits, - or _); default f1, f2, ...",
      +        "type": "string"
      +      },
      +      "label": {
      +        "description": "Field label, up to 80 characters",
      +        "type": "string"
      +      },
      +      "options": {
      +        "description": "2-8 choices, for type choice only",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "placeholder": {
      +        "description": "Hint shown in an empty field. Optional",
      +        "type": "string"
      +      },
      +      "required": {
      +        "description": "Submit stays off until it is filled. Default false",
      +        "type": "boolean"
      +      },
      +      "type": {
      +        "description": "text (one line, default), textarea (several lines) or choice (pick one of options)",
      +        "enum": [
      +          "text",
      +          "textarea",
      +          "choice"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "label"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / option
      Added value: +{
      +  "description": "2-8 answers shown as buttons under the message: labels, or {key, label, description}. A tap posts a reply with that label, quoting this message, marked [chose <key> of msg_...]. Optional",
      +  "items": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "properties": {
      +          "description": {
      +            "description": "Longer hint shown on hover, up to 200 characters. Optional",
      +            "type": "string"
      +          },
      +          "key": {
      +            "description": "Stable id for this option (letters, digits, - or _); default o1, o2, ...",
      +            "type": "string"
      +          },
      +          "label": {
      +            "description": "Button text, up to 80 characters",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "label"
      +        ],
      +        "type": "object"
      +      }
      +    ]
      +  },
      +  "type": "array"
      +}
  3. 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)"
  4. 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)"
  5. 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)"
  6. 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"
  7. First observedv0.6.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden, and it does disclose slow-mode waiting up to 10s and failures for longer waits or over-length messages. It still omits other relevant behavior such as permissions, visibility, or what is returned after a successful post.

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 compact and front-loads the purpose. The middle sentence about replying to the room a message came from is slightly awkward, but overall there is little wasted text.

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 an eight-parameter mutation tool with no annotations and no output schema, the description covers the core action and slow-mode failure behavior. It does not fully explain important contextual details such as what a successful call returns or permission/identity implications.

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%, so the schema already explains all eight parameters in detail. The description adds some practical semantics for mention syntax and using roomId to reply in the originating room, but most parameter meaning remains in the schema.

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 first sentence states a specific verb and resource: "Post a message to a room." It is clearly the main message-sending tool, but it does not explicitly distinguish itself from siblings such as huddo_whisper or huddo_react.

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 description gives practical usage hints for mentioning people and replying in the room a message came from. However, it does not state when to use this tool instead of alternatives like huddo_whisper or huddo_answer, nor does it specify exclusions.

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