Skip to main content
Glama

Send a message

messages_send
Destructive

Sends the message shown by messages_preview to the one dealership on one row of a request. It reaches a real dealership and cannot be undone. It takes the previewToken that messages_preview returned for the same text, the same row and the same idempotencyKey. A call repeated with the same idempotencyKey returns the first answer and sends no second message.

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": {
      "dealSetId": "<dealSetId>",
      "rowKey": "<rowKey>",
      "text": "<text>",
      "previewToken": "<previewToken>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "messages_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe message text, as the buyer wants it said to the dealership.
askIdNoOptional. The `askId` of the dealership's question this message answers, from a message in `messages_list` that carries one. Leave it out if the message answers no question. The preview and the send take the same `askId`.
intentNoPractice requests only. Marks this message as asking the dealership for a lower price, when the buyer asked for one.
rowKeyYes
dealSetIdYesThe id of the request, from requests_list.
previewTokenYesThe previewToken that messages_preview returned for this exact text, this row and this idempotencyKey. Valid for 15 minutes.
idempotencyKeyYesA key made up for this one message. The preview and the send take the same key; sending the same key again returns the first answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description adds real value by explaining the irreversible real-world effect and idempotency behavior. It does not cover authentication, rate limits, or error behavior, but the safety-critical traits are well disclosed.

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?

The definition is four sentences and front-loads the core action before adding the irreversible-effect warning and idempotency rule. Every sentence contributes necessary context without redundant wording.

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 destructive, open-world mutation tool with seven parameters and no output schema, the description covers the safety-critical prerequisites and idempotency behavior. It leaves response shape and error handling unstated, but the most important operational context is present.

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 high at 86%, so the schema already documents parameters such as previewToken and idempotencyKey thoroughly. The description reinforces the cross-parameter requirement that previewToken, text, row, and idempotencyKey must match the preview call, but it largely repeats what the schema already provides.

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 states a specific verb and resource: it sends the message shown by messages_preview to one dealership on one row of a request. It clearly distinguishes this write action from the preview sibling by requiring the previewToken returned for the same text, row, and idempotencyKey.

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 establishes the prerequisite that messages_preview must be called first and that the same text, row, and idempotencyKey must be reused. It also warns that the action reaches a real dealership and cannot be undone, though it does not explicitly name when not to use this tool or describe alternative paths.

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