Graylog MCP Server

get_message

Fetch the full untruncated log message document using its _id and _index from a search result, to inspect individual hits in detail.

Instructions

Fetch the full, untruncated document for a single message by its _id and _index (both returned by search). Use after a concise search to inspect one hit in full.

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": {
      "messageId": "<messageId>",
      "index": "<index>"
    },
    "name": "get_message"
  }
}

Input Schema

Name	Required	Description
`index`	Yes	The message _index from a search result.
`instance`	No	Graylog instance to query. Active: "instance_1". Default: "instance_1".
`messageId`	Yes	The message _id from a search result.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the returned document is 'full, untruncated' unlike search results, but doesn't cover error behavior, auth requirements, or exact return structure.

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 focused sentences, front-loaded with action and resource. No redundant wording or unnecessary detail.

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 simple fetch operation with fully documented schema and clear usage guidance, the description is sufficient. It explains what the tool returns ('full document') and when to use it, making it complete without an output schema.

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 covers all 3 parameters with descriptions. The description adds the crucial context that '_id' and '_index' are 'both returned by search', linking parameters to their source, which goes beyond 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 clearly states 'Fetch the full, untruncated document for a single message' with specific identifiers (_id and _index), distinguishing it from the sibling 'search' which returns concise results.

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?

Explicitly states 'Use after a concise search to inspect one hit in full', providing a clear when-to-use. It does not mention exclusions or alternatives, but none are relevant among the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server