Skip to main content
Glama

Reply to a message

event_reply

Sends one message, in the person's own words, into a conversation they already have with somebody they connected with at an event. Needs a personal connector token (a shared token reads and sends nothing), text, and the conversation as firstName (as event_inbox spelled it) or chatId (as event_inbox returned it). The message is delivered when the call returns and cannot be unsent. It sends as that person into their own conversation only; the server checks this on every call and refuses with NOT_PARTICIPANT otherwise. A firstName that matches two of their conversations returns AMBIGUOUS_NAME and sends nothing. The app's own cooldown, flood limit and content rules apply, because it is the same send; RATE_LIMITED means messages are going out too fast. Returns ok:true when sent, which says nothing about whether the other person has read it or will reply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe message in the person's own words, up to 1000 characters. It is sent as given.
chatIdNoOptional. The id of the conversation, as an event_inbox thread row gave it. When both this and firstName are sent, this one is used.
firstNameNoOptional. The first name of the person to answer, as an event_inbox thread row spelled it, matched against the caller's own conversations only. Two matches return AMBIGUOUS_NAME and nothing is sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / chatId / description
      Previous value: -"OPTIONAL. The id of the conversation to send into, exactly as an event_inbox thread row gave it. Never construct one. Pass this OR firstName, not both; passing both uses this one."New value: +"Optional. The id of the conversation, as an event_inbox thread row gave it. When both this and firstName are sent, this one is used."
    • changedInput schema / properties / firstName / description
      Previous value: -"OPTIONAL. The FIRST NAME of the person to answer, exactly as an event_inbox thread row spelled it. Matched against the caller's OWN conversations only. Two matches come back AMBIGUOUS_NAME and NOTHING IS SENT, and you ask which one they mean rather than choosing: there is no way to unsend a message to the wrong person."New value: +"Optional. The first name of the person to answer, as an event_inbox thread row spelled it, matched against the caller's own conversations only. Two matches return AMBIGUOUS_NAME and nothing is sent."
    • changedInput schema / properties / text / description
      Previous value: -"REQUIRED. The message, in the PERSON'S OWN WORDS, up to 1000 characters. Send what they said: do not tidy it, do not shorten it, do not improve it and never invent one. If they have not said what to send, ask them instead of calling this."New value: +"The message in the person's own words, up to 1000 characters. It is sent as given."
  2. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources