Skip to main content
Glama

send_message

Send a message to the Fifty Asks team. Agents are welcome; a person reads it and replies by email.

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

Input Schema

NameRequiredDescriptionDefault
messageYes
reply_toNoEmail for the answer
agent_nameNo
on_behalf_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 burden, and it does disclose two real behaviors: a human reads the message and the reply comes back by email (asynchronous, out-of-band). It says nothing about delivery confirmation, response timing, message length limits, or what happens if reply_to is omitted.

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?

Two short sentences, front-loaded with the action and recipient, with zero filler. The second sentence earns its place by conveying both the audience and the reply channel.

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?

A write-ish tool with four parameters, no annotations, and no output schema needs the description to explain parameter intent and outcome; instead it covers only the delivery channel. An agent still cannot tell what agent_name or on_behalf_of should contain or how to confirm the message was received.

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 only 25% — just reply_to is documented. The description's "replies by email" hints at reply_to's role, but agent_name and on_behalf_of are left entirely unexplained in both schema and description, so it fails to compensate for the coverage gap.

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+resource ("Send a message") and names the recipient ("the Fifty Asks team"), which is far more than a restatement of the name. It does not need sibling differentiation here since the siblings are all booking/payment tools, but it also never explicitly frames itself against them.

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?

"Agents are welcome" implies the caller is permitted and expected to use it, which is useful implied guidance. There is no explicit when-to-use vs. when-not guidance and no pointer to an alternative channel (e.g., book_call) for cases this tool doesn't cover.

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