Skip to main content
Glama

reply

Destructive

Send a private message in your item, Support or Wanted conversation; recipients may receive notifications. Support and Wanted replies are free; use their explicit thread_kind. A message never makes or accepts an offer. Approve max_fee; exact request_id retries do not duplicate messages or fees.

Input Schema

NameRequiredDescriptionDefault
lot_idNo
saleIdNo
max_feeYes
messageYes
request_idYes
thread_kindNo
conversation_idNo
expected_revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / $defs / 1
      Added value: +{
      +  "maxLength": 256,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / anyOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "saleId": false
      -    },
      -    "required": [
      -      "thread_kind"
      -    ]
      -  },
      -  {
      -    "properties": {
      -      "expected_revision": false,
      -      "thread_kind": false
      -    }
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "lot_id": false,
      +      "saleId": false
      +    },
      +    "required": [
      +      "thread_kind"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "expected_revision": false,
      +      "thread_kind": false
      +    }
      +  }
      +]
    • addedInput schema / properties / lot_id
      Added value: +{
      +  "$ref": "#/$defs/1"
      +}
    • addedInput schema / properties / saleId / $ref
      Added value: +"#/$defs/1"
    • removedInput schema / properties / saleId / maxLength
      Removed value: -256
    • removedInput schema / properties / saleId / minLength
      Removed value: -1
    • removedInput schema / properties / saleId / type
      Removed value: -"string"
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag this as a non-readonly, open-world, destructive operation. The description adds useful behavior beyond that: recipients may be notified, Support/Wanted replies are free, max_fee must be approved, and exact request_id retries do not duplicate messages or fees.

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 description is compact and front-loads the main action before adding constraints. The final two clauses are dense but each conveys non-obvious behavior rather than restating the tool name.

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?

For an 8-parameter mutation tool with no output schema and 0% schema description coverage, the definition leaves too many parameters undocumented. It does not explain expected_revision, conversation_id, or how lot_id/saleId relate to the conversation scenarios.

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 0%, so the description must compensate. It explains thread_kind, max_fee approval, and request_id retry semantics, but leaves message, conversation_id, expected_revision, lot_id, and saleId unexplained.

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 private message' in item, Support, or Wanted conversations. It also distinguishes the action from making an offer, which helps separate it from the sibling 'offer' tool.

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?

It gives some context: use explicit thread_kind for Support/Wanted, and messages never create offers. However, it does not clearly say when to use this tool versus siblings like 'respond' or 'offer', leaving the agent to infer the boundary.

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