Skip to main content
Glama
Sign In
@kieksme/listmonk-mcp

@kieksme/listmonk-mcp

by kieksme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Server Logs

listmonk_get_logs
Read-onlyIdempotent

Retrieve recent in-memory application log entries from Listmonk to inspect runtime events and diagnose issues.

Instructions

Returns Listmonk's recent in-memory application log entries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listmonk_get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description earns credit for adding that the logs are in-memory and therefore recent/volatile and bounded, which is real behavioral context. It does not disclose how many entries are returned, whether output is buffered per-request or global, or any log-level filtering.

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?

One sentence, front-loaded with the verb and resource, no filler or redundant restatement of the title. Nothing to trim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no output schema, and only annotation-level safety info, the description is the sole source of detail — and it never describes the return shape of a log entry (timestamp, level, message) or the approximate volume. For a diagnostics tool an agent may need to parse results from, that is a meaningful gap, though the core operation is simple enough that the omission is not fatal.

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?

The tool takes zero parameters, so the baseline is 4, but the description offers no guidance on the implicit dimensions an agent might otherwise control — no note that there is no level/limit/since parameter, which would tell the agent it cannot narrow the result. Falling slightly below baseline for leaving that implication unstated.

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 gives a specific verb and resource ("Returns ... application log entries") and the qualifier "recent in-memory" separates it from the similarly named listmonk_get_import_logs sibling. It stops short of explicitly naming that sibling as the alternative, so differentiation requires a small inference.

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?

There is no when-to-use guidance at all — nothing says this is a diagnostics/troubleshooting tool versus a data-retrieval tool. With dozens of siblings including listmonk_get_import_logs, listmonk_get_health, and listmonk_get_server_config, the agent gets no routing help for choosing among observability tools.

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

Deploy Server

Other Tools