Skip to main content
Glama
Sign In
o3de-mcp

o3de-mcp

by nickschuetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tail_log

Troubleshoot O3DE errors by reading the last N lines of a log file, with optional line count and filter.

Instructions

Read the last N lines of an O3DE log file.

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": {
      "log_name": "<log_name>"
    },
    "name": "tail_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNo
filterNo
log_nameYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, 'Read' conveys a non-mutating operation and 'last N lines' clarifies it does not return the full log, so the core behavioral trait is present. It does not disclose edge cases such as missing log files or path resolution behavior, and it does not mention that filtering exists, leaving some behavior implicit.

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 with no filler; the resource, operation, and scope are all front-loaded and every word contributes. This is an appropriately sized description for a simple read tool.

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

Completeness2/5

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

Despite the output schema covering return values and the property names being intuitive, the tool has four parameters and zero schema descriptions. An agent cannot tell what filter matches against, how project_path resolves the log, or how log_name identifies the log, so the description is not complete enough for reliable invocation.

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% and the description must compensate for all four parameters, but it only hints at 'lines' through 'last N lines'. The required log_name and the optional filter/project_path semantics are left entirely to inference from property names and defaults.

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 uses a specific verb ('Read') and resource ('O3DE log file') and adds the tail behavior ('last N lines'), making the tool's purpose immediately clear. It is distinct enough from siblings like get_log_errors or create_level, though it does not explicitly name a sibling.

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 guidance about when to choose tail_log over related log tools such as get_log_errors, nor any exclusions or prerequisites. The only usage signal is the implied 'when you need the tail of an O3DE log,' which is not explicit.

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