Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

Read Service Logs

readServiceLogs
Read-only

Fetches the last 200 log lines for a Compose service container, returning logs and container state; stream via SSE to follow live output.

Instructions

Returns the last 200 log lines of one container as {container, state, logs}; state is no-pod when nothing is running. serviceName is a compose service. Sending Accept: text/event-stream instead follows the log live as server-sent events, one bare data: frame per line, which never completes on its own.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "appSlug": "<appSlug>",
      "serviceName": "<serviceName>"
    },
    "name": "readServiceLogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
regionNo
appSlugYes
serviceNameYes
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.7/5.0
Behavior5/5

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

The annotations already declare this a non-destructive, read-only, open-world operation, and the description adds behavior they cannot express: a hard 200-line cap, a `no-pod` sentinel state when nothing is running, and the fact that the SSE variant never terminates on its own. That last detail is a real operational hazard the agent would otherwise miss, and it is precisely the kind of disclosure annotations do not cover.

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?

Three sentences, each carrying distinct load: return payload and size cap, the meaning of the key input, then the streaming variant and its termination caveat. Nothing is repeated and the most decision-relevant facts come first.

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 output schema, the description usefully specifies the return shape and the `no-pod` state, and it covers the unusual streaming mode. What it omits is input semantics for four of five parameters, so an agent still cannot tell what `env` or `region` select without guessing. Adequate on outputs, incomplete on inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description carries the full burden and largely does not meet it. Only `serviceName` gets meaning ('is a compose service'); `workspaceSlug`, `appSlug`, `env` and `region` are undocumented in both schema and description, including the enum values for `env`. One of five parameters explained is thin compensation for a zero-coverage schema.

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 opens with a concrete verb and resource: it returns 'the last 200 log lines of one container', and even fixes the response shape as `{container, state, logs}`. That is far more specific than the bare name 'readServiceLogs'. It stops short of naming the log-related siblings (queryAppLogs, streamDeployLogs, readServiceJobDetails), so sibling differentiation is left to inference.

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?

There is no explicit statement of when to choose this tool over queryAppLogs or streamDeployLogs. The 200-line snapshot framing and the note about the `Accept: text/event-stream` alternative imply the trade-off between a one-shot read and a live follow, but the agent has to derive that itself. Guidance is implied, not stated.

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