Skip to main content
Glama

messages_hide

DestructiveIdempotent

Hide a log message 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>",
      "messageId": "<messageId>"
    },
    "name": "messages_hide"
  }
}

Input Schema

NameRequiredDescriptionDefault
logIdYesThe ID (Guid) of the log.
messageIdYesThe ID of the message to hide.
markAllAsHiddenNoIf true, also hides every other message with the same grouping hash.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so 'Changes data' largely restates structured data. The genuinely additive content is the confirmation protocol before mutating, which is useful but only one extra fact for a destructive operation with a bulk side-effect flag.

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 short sentences, action first and safety instruction second, with no redundant or filler 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 three-parameter destructive mutation with rich annotations and a fully described schema, the description covers what it does and the confirmation requirement. It could note that the change is reversible via messages_unhide, which matters for a destructive tool, but nothing essential to calling it correctly 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 description coverage is 100% and every parameter, including the default on markAllAsHidden and its grouping-hash semantics, is documented in the schema. The description adds only 'by ID', so 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?

States a specific verb and resource ('Hide a log message by ID'), which is unambiguous and separable from messages_unhide/messages_get in the sibling list. It does not explicitly name those siblings, but the action is clear enough to select without opening the 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?

Gives an explicit precondition for acting: unless the user requested exactly this change, enumerate the affected messages and obtain confirmation first. It stops short of naming messages_unhide as the inverse operation or explaining when hiding is preferable to messages_fix, so it is strong but not a full when/when-not map.

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