Skip to main content
Glama

get_service_logs

Retrieve a service's stdout/stderr and system event logs, including startup, crashes, and out-of-memory events; pass the previous cursor to fetch new log lines.

Instructions

Servisin çalışma logları (stdout/stderr + sistem olayları: başlatma, çökme, bellek aşımı). Yeni satırlar için önceki yanıttaki cursor'ı after olarak ver.

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

Input Schema

NameRequiredDescriptionDefault
afterNo
linesNo
serviceIdYesServis id (list_services / create_service yanıtındaki id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses what the output contains (stdout/stderr and system events such as crashes and OOM) and the cursor-based continuation model. It omits retention window, ordering (oldest vs newest first), default line count, permission requirements, and whether logs are truncated at the 1000-line cap.

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 sentences, zero filler, with the content scope front-loaded and the pagination instruction second. Nothing could be removed without losing information.

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?

For a read-only log retrieval tool with no annotations and no output schema, the description should state the return shape — at minimum that a cursor field is returned alongside entries and in what order lines arrive. It hints at a cursor implicitly but never confirms the response structure, and the default for `lines` is unstated.

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 33%: only `serviceId` is documented in the schema. The description compensates for `after` by explaining it is the cursor from the previous response, but says nothing about `lines` (default value, effect of the 1000 maximum), so half the undocumented parameters remain opaque.

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 states a specific resource and content type: the service's runtime logs, explicitly stdout/stderr plus system events (startup, crash, OOM). This is clearly distinguishable from siblings like get_service (metadata) or get_build, even though no alternative is named explicitly.

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?

It gives one concrete usage rule — pass the cursor from the previous response as `after` to fetch new lines — which implies incremental polling. It does not say when to prefer this over get_service or exec_in_service, nor whether it is a one-shot dump or a polling tool, leaving the choice largely to inference.

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