Skip to main content
Glama

Preview a message

messages_preview
Read-only

Shows the exact message that messages_send would send to one dealership, and sends nothing. It answers with the text as the dealership would get it, how it would be sent (sms or email), whether it can be sent now, and a previewToken that is valid for 15 minutes and only for this exact text, this row and this idempotencyKey.

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>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "messages_preview"
  }
}

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`.
rowKeyYes
dealSetIdYesThe id of the request, from requests_list.
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.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds substantial context on top: what the response contains (rendered text, channel, sendability), and the critical constraint that the previewToken expires in 15 minutes and is bound to this exact text, row, and idempotencyKey. That token-binding behavior is exactly the kind of detail an agent cannot infer from annotations or schema.

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?

The scope statement is front-loaded in the first clause, and the second sentence enumerates the returned facts without filler. The parenthetical channel list and the stacked token qualifiers make the tail dense, but every element carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry the return contract, and it does — text, channel, sendability, and token. The token's lifetime and scoping are spelled out, which is the only non-obvious behavioral fact for a five-parameter preview tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is a 3, and the description earns above that by tying the previewToken to the specific text, row, and idempotencyKey parameters — implying that altering any of them invalidates the token. It does not restate the askId or dealSetId semantics, but those are already documented in the schema.

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 opens with a specific verb and resource ("Shows the exact message that messages_send would send to one dealership") and immediately distinguishes itself from its closest sibling by stating "and sends nothing." An agent can tell what this does and how it differs from messages_send without opening either schema.

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?

The dry-run framing plus "sends nothing" makes the selection condition against messages_send clear, and the previewToken note implies this is a verification step before sending. It stops short of an explicit "call this before messages_send" instruction or any statement about when a preview is unnecessary.

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