Skip to main content
Glama
Sign In
infra-mcp

infra-mcp

by esp4ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_service_logs

Retrieve bounded journald logs for a service, filtered by severity level, with server-side line capping.

Instructions

Returns bounded journald logs for a service, filtered by severity level. Filtering and line-capping execute on the VM before transmission.

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": {
      "vm": "<vm>",
      "service": "<service>"
    },
    "name": "get_service_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmYesVM name as defined in infra-mcp.yaml
serviceYessystemd service name; must be in the VM's allowlist
levelNoMinimum severity to include: error | warning | info | debugerror
linesNoMaximum lines to return; server-capped at 200

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.2
    • addedInput schema / properties / level / description
      Added value: +"Minimum severity to include: error | warning | info | debug"
    • addedInput schema / properties / lines / description
      Added value: +"Maximum lines to return; server-capped at 200"
    • addedInput schema / properties / service / description
      Added value: +"systemd service name; must be in the VM's allowlist"
    • addedInput schema / properties / vm / description
      Added value: +"VM name as defined in infra-mcp.yaml"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Discloses that filtering and line-capping execute on the VM before transmission, adding value beyond no annotations. However, lacks details on error handling or authentication needs.

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 efficient sentences with no waste, front-loaded with the core action and a key behavioral detail.

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?

With output schema present, return value explanation not needed. Covers core functionality but misses edge cases like invalid VM/service. Adequate for a straightforward log retrieval tool.

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 good parameter descriptions. The description adds only the processing location context; does not significantly enhance understanding beyond 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 it returns bounded journald logs for a service filtered by severity level, specific verb+resource with clear scope, distinguishing from siblings like get_audit_log or get_log_file.

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?

No explicit guidance on when to use versus alternatives. Implied usage for service logs, but lacks when-not-to-use or comparison with 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

Other Tools