Skip to main content
Glama

thanaton_get_logs

Retrieve real-time stdout and stderr logs from a deployed Thanaton project workload to diagnose runtime behavior and troubleshoot issues.

Instructions

Retrieve real-time runtime stdout/stderr logs from a deployed Thanaton project workload.

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": {
      "project_slug": "<project_slug>"
    },
    "name": "thanaton_get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_slugYesTarget project slug or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and does not meet it: it never says whether logs are streamed, polled once, or tailed for a bounded window, how much history is returned, or whether the call blocks. It also omits any permission or deployment-state requirements, which matters since it targets a 'deployed' workload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and the resource, with no filler or redundancy. It is efficient, though its brevity is also the source of the missing behavioral detail rather than a virtue in itself.

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 one-parameter read tool with no output schema and no annotations, an agent still needs to know the return shape (raw log lines vs structured entries) and the semantics of 'real-time'. Neither is covered, so the definition is minimally viable but leaves real gaps.

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 description coverage is 100% for the single project_slug parameter, so the schema already explains that it accepts a slug or ID. The description adds no further parameter meaning, which is the baseline-3 case when the schema does the heavy lifting.

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?

States a specific verb (Retrieve) and a well-defined resource (real-time runtime stdout/stderr logs) scoped to a deployed Thanaton project workload. That scope separates it from configuration-oriented siblings such as thanaton_manage_log_drains, though no sibling 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 Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites, and no alternative tools for related needs (e.g., log drains or historical queries). The only hint is the word 'real-time', which implicitly contrasts with non-real-time log sources but is never stated as a selection rule.

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