Skip to main content
Glama

messages_bot

DestructiveIdempotent

Mark log messages as bot-generated by ID. Changes data. Unless the user asked for exactly this change, say which messages you will change and get their confirmation first.

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": {
      "logId": "<logId>",
      "messageIds": "<messageIds>"
    },
    "name": "messages_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
logIdYesThe ID (Guid) of the log.
messageIdsYesIDs of the messages to mark as bot (1-500 per call).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / logId / type
      Added value: +"string"
    • addedInput schema / properties / messageIds / items / type
      Added value: +"string"
  2. Changed2 schema fields changed
    • removedInput schema / properties / logId / type
      Removed value: -"string"
    • removedInput schema / properties / messageIds / items / type
      Removed value: -"string"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so 'Changes data' is largely redundant. However, the description adds a genuinely new behavioral requirement not in annotations: disclose the exact messages to be changed and obtain user confirmation first. It doesn't mention reversibility (messages_unbot exists) or scope/rate considerations.

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?

Two short sentences, front-loaded with the action and followed by the safety rule. 'Changes data' is slightly redundant with the destructiveHint annotation but serves as a fast warning.

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?

For a two-parameter mutation with full schema coverage and complete annotations, the description covers the action, the mutation risk, and the required confirmation workflow. No output schema exists, and nothing essential for a correct invocation is missing.

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 coverage is 100%, with logId and messageIds fully documented including the 1-500 message limit. The description only adds 'by ID' emphasis, contributing no meaning beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ('Mark log messages as bot-generated by ID'), which is clearly distinct from siblings like messages_unbot and messages_bot_by_query. It does not explicitly name the alternatives, but the operation is unambiguous.

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 a strong procedural rule for confirmation before mutating, but offers no guidance on when to choose this tool over messages_bot_by_query or when unmarking with messages_unbot is appropriate. Usage context is implied by 'by ID' rather than stated.

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