Skip to main content
Glama

client_get_logs

Read-only

Read local FiveM client logs to inspect Lua prints, script errors, and NUI console output; filter by level, resource, or text and use the after cursor to fetch newer lines.

Instructions

Read the local FiveM client log: client Lua prints and script errors plus NUI console output. Pass next as after to read only newer lines.

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": "client_get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
levelNo
limitNo
containsNo
resourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds useful context about what the log contains (client Lua prints, script errors, NUI console) and the cursor-based incremental read behavior. It says nothing about default/maximum result counts or ordering, which matter for a log reader.

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 resource and content scope front-loaded before the incremental-read hint. Every sentence carries information.

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?

For a five-parameter tool with no output schema and no parameter descriptions, the definition is thin: filtering by level, contains, and resource is never explained, nor is the meaning of the 'next' cursor the caller is told to pass back. An agent could invoke it, but only with blind parameters.

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 must compensate and largely does not. It explains only 'after' (and that the value comes from a 'next' cursor), leaving level, limit, contains, and resource entirely undocumented in both schema and prose.

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 and resource: 'Read the local FiveM client log', and enumerates the content types (Lua prints, script errors, NUI console output). The word 'client' implicitly distinguishes it from the sibling server_get_logs, but it never names that sibling 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?

The only usage guidance is the incremental-read instruction ('Pass next as after to read only newer lines'), which implies a follow-up polling pattern. There is no statement of when to prefer this over server_get_logs or resource_get_diagnostics, nor any exclusions.

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