Skip to main content
Glama

resource_get_diagnostics

Read-only

Retrieves a FiveM resource's live state, file path, and recent server errors by resource name to diagnose runtime issues.

Instructions

Live resource state, path and its recent server errors

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": {
      "resource": "<resource>"
    },
    "name": "resource_get_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverNo
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds a small amount of value by stating what the response contains (live state, path, recent server errors), which is useful since no output schema exists. It still says nothing about scope, freshness, or error-window limits.

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

Conciseness3/5

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

It is short and front-loaded with no filler, but the single telegraphic fragment reads like a truncated field list rather than a complete statement, which hurts interpretability more than it saves space.

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?

With two undocumented parameters, a required 'resource', an unexplained optional 'server', and no output schema, the description should clarify input meaning and response shape. It only gestures at the response contents, so the definition is not complete enough for an agent to call it confidently.

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%, so the description must carry parameter meaning and does not. 'Resource' is echoed but never explained, and the optional 'server' parameter is not mentioned at all, leaving the agent to guess whether omitting it selects a default server or all servers. The word 'path' in the description does not map to any schema property.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Live resource state, path and its recent server errors' names the resource and the diagnostics payload, so the agent can roughly infer a retrieval of a resource's live state and error log. However, it is a noun phrase with no verb, and it never distinguishes itself from the closely named sibling server_get_diagnostics.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as server_get_diagnostics or resource_read. The agent must guess whether this is for troubleshooting a specific failing resource versus general state inspection.

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