Skip to main content
Glama
Sign In
yafmcp

yafmcp

by mri-Qbox-Brasil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Ler os arquivos de log do servidor

fivem_logs

Reads txAdmin/FXServer log files to inspect console output and admin actions. Use sinceBoot, regex filtering, and file listing to find errors after the last server start or review past days.

Instructions

Lê os arquivos de log do txAdmin (txData//logs): fxserver.log é o console do dia inteiro, inclusive de antes desta sessão e de boots anteriores; os dias passados ficam em fxserver_AAAA-MM-DD_*.log, e admin.log tem as ações dos admins. Use sinceBoot para ver só o que veio depois do último start do servidor, filter (regex, sem diferenciar maiúsculas) para achar erros, e list para ver os arquivos.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fivem_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoArquivo da pasta de logs (padrão fxserver.log)
listNoLista os arquivos de log em vez de ler
linesNoQuantas linhas do fim (padrão 200)
filterNoRegex case-insensitive para filtrar as linhas
sinceBootNoSó a partir do último "FXServer Starting"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and largely meets it: it discloses that fxserver.log spans the entire day including pre-session and previous boots, and that historical days are rotated into dated files — the key behavioral fact an agent needs to interpret results. It stops short of stating read-only semantics explicitly or what happens when a file is absent, and there is no output schema to compensate.

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?

The what-and-where is front-loaded before the parameter advice, and the sentence structure maps cleanly onto the file layout then the three useful flags. A little length is spent re-explaining schema-level details like the case-insensitive regex.

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?

For a five-optional-parameter read tool with no output schema and no annotations, the definition covers file locations, rotation, admin actions, and the narrowing flags. It leaves the `lines` tail behavior to the schema and says nothing about missing files or volume limits, which are minor residual 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 coverage is 100%, so all five parameters are already documented in the input schema, including defaults for file and lines. The description restates filter's case-insensitivity and sinceBoot's 'FXServer Starting' anchor almost verbatim, adding only marginal framing about why those knobs exist. Baseline 3 is appropriate.

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 specific verb and resource ('Lê os arquivos de log do txAdmin') and immediately grounds it in a concrete location (txData/<perfil>/logs) and file taxonomy (fxserver.log, fxserver_AAAA-MM-DD_*.log, admin.log). It does not explicitly contrast itself with the sibling fivem_console, so an agent must infer the difference between reading archived log files and a live console.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives per-parameter usage conditions: sinceBoot for post-restart content, filter (regex, case-insensitive) to hunt errors, list to enumerate files instead of reading. What's missing is an explicit statement of when to prefer this over fivem_console, or when not to use it at all.

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