Skip to main content
Glama

send_message

Send a message to the human operator about a quote or task. The operator's replies appear in the messages of get_task_status.

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

Input Schema

NameRequiredDescriptionDefault
idYes
messageYesPlain text, 1-2000 characters.
access_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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. It discloses the recipient (a human operator) and the reply channel (get_task_status messages), which is genuinely useful behavior beyond the schema. It does not say whether delivery is immediate or asynchronous, whether the message is persisted, or what happens on failure.

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 sentences with no filler; the action comes first and the reply-location note follows as supporting context. Every clause earns its place.

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 a three-required-parameter tool with no annotations and no output schema, the description covers intent and reply routing but leaves the critical unresolved question of what 'id' refers to and whether authentication is handled by 'access_token' or elsewhere. Adequate but with a clear gap an agent would hit on first invocation.

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 coverage is only 33%: 'message' is documented (plain text, 1-2000 chars) in the schema, but 'id' and 'access_token' are undocumented anywhere. The description's 'about a quote or task' weakly hints that 'id' identifies a quote or task but never confirms it, so the meaning of a required identifier parameter is left ambiguous.

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 description states a specific verb and resource: send a message to the human operator, scoped to a quote or task. It is clearly distinguishable from siblings like get_task_status, accept_quote, and request_quote, though it does not explicitly name a non-overlapping alternative.

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?

Usage is implied by the phrase 'about a quote or task', which tells the agent this is for operator communication relating to a quote or task. It also usefully says replies surface in get_task_status, but there is no explicit when-to-use/when-not guidance or statement of prerequisites such as which id to supply.

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