Graylog MCP Server

import_log_templates

Import log templates into the active connection's library, choosing merge to preserve existing templates or replace to overwrite them.

Instructions

Import templates into the active connection's library.

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": {
      "templates": "<templates>"
    },
    "name": "import_log_templates"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	merge keeps existing; replace wipes first. Default 'merge'.
`templates`	Yes	Map of templateId → template object

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/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 of behavioral disclosure. It only states the import action and target; it does not mention that 'replace' mode is destructive, that existing templates may be wiped, or any side effects. It also does not explicitly state the requirement for an active connection as a prerequisite.

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?

The description is a single concise sentence that immediately states the action and target. It contains no wasted words or redundant information.

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?

Despite the schema being complete, the description is too sparse for a mutation tool without annotations or an output schema. It omits return value information, behavioral side effects, and prerequisites, leaving the agent with insufficient context to invoke the tool safely and effectively.

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?

All parameters are fully described in the input schema (coverage 100%), with mode explaining merge vs replace and templates describing the map. The description adds no additional parameter semantics beyond what the schema already provides, so a baseline of 3 is appropriate.

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 uses the specific verb 'import' with resource 'templates' and a clear destination 'active connection's library.' This distinguishes it from sibling tools like export_log_templates, list_log_templates, and delete_log_template by action and target.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites (e.g., establishing an active connection). It is a bare statement of action without context.

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