Skip to main content
Glama

Send a message

send_message

Send a message to an entry for the user: a question, or anything they want its owner to know. Only for entries whose actions (get_entry_sections) list send_message. Ask the user for their name and email address. Nothing is sent by this call: the user sends it on Daawid's page, with a code Daawid emails them. Give the user the link from the answer.

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": {
      "entry": "<entry>",
      "requester": "<requester>",
      "subject": "<subject>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYesWhich entry: its ID or slug, from search or get_entry.
answersNoAnswers to the action's own questions (get_entry_sections), by their keys.
messageYesThe message, in the user's words and language. Show it to them; don't add what they didn't say.
subjectYesWhat the message is about, in a few words.
actionIdNoWhich of its actions of this kind (get_entry_sections), when it has several.
requesterYes
idempotencyKeyNoYour own key for this request: the same key and details within 24 hours give the same request.

Output Schema

NameRequiredDescriptionDefault
urlNo
kindYes
entryYes
runIdNo
statusYes
summaryYes
expiresAtNo
confirmUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses the single most important non-obvious behavior: nothing is actually sent by this call, the user completes the send on Daawid's page with an emailed code. It also tells the agent what to do with the result (give the user the link from the answer), which annotations like openWorldHint and destructiveHint=false cannot convey.

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?

Four short sentences, front-loaded with the action and the eligibility gate before the important caveat that nothing is sent. Dense but every sentence carries information; the phrasing is slightly clipped but not padded.

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?

For a 7-parameter, nested-object tool with an output schema and high schema coverage, the description supplies the pieces structured fields cannot: eligibility, the deferred-send mechanic, and the follow-up action. Minor gaps (how answers map to the action's questions, what the returned link looks like) are covered by schema and output schema.

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 86%, so entry, requester, subject, message, answers and actionId are already documented in the schema. The description reinforces that the requester's name and email must come from the user rather than being guessed, but adds little beyond what the parameter descriptions already state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (send a message to an entry) and narrows the scope to questions or information the user wants the entry's owner to know. It also names the gate (entries whose actions list send_message) and the sibling used to check it, so the agent can distinguish this from get_entry or request_* siblings.

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

Usage Guidelines4/5

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

It gives an explicit precondition — only use for entries whose actions from get_entry_sections list send_message — plus a concrete procedural step (ask the user for name and email). It stops short of naming when to prefer the request_appointment or request_quote siblings instead, leaving that routing to the action list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources