Skip to main content
Glama

performance_get_resource

Read-only

Retrieves mean, p95, and max tick timings for a FiveM resource from a saved profile ID, helping identify performance bottlenecks.

Instructions

Resource tick timing (mean, p95, max ms) from a saved profile ID

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>",
      "profileId": "<profileId>"
    },
    "name": "performance_get_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverNo
resourceYes
profileIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds that the output is timing statistics with named percentiles, which is useful context beyond the annotations, but it says nothing about aggregation windows, missing-profile behavior, or units semantics beyond 'ms'.

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?

A single front-loaded sentence with no filler; the metric list is the most informative part and appears early. It is efficient, though its brevity contributes to the missing guidance rather than being purely economical.

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 tool with three parameters, no output schema, and none of the schema descriptions filled in, a one-line description is not enough. An agent still does not know what the server parameter does, how profiles are created or found, or how to interpret the returned statistics.

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 three parameters, so the description must carry the explanatory load. It clarifies profileId as a 'saved profile ID' and implies the resource parameter, but the server parameter is never mentioned and no parameter format or scoping rules are given.

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 names a specific resource (resource tick timing) and the exact metrics returned (mean, p95, max ms), plus the data source (a saved profile ID). That is clear enough for an agent to recognize a read of performance metrics, but it does not distinguish this from siblings like performance_get or performance_profile, so it falls short of a 5.

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 statement of when to use this tool versus performance_get, performance_profile, or the diagnostics tools. The phrase 'from a saved profile ID' hints at a prerequisite but never says how to obtain one or what happens without a profile.

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