Skip to main content
Glama

nui_eval

Destructive

Evaluates a JavaScript expression in a FiveM resource's NUI page, awaits promises, and returns JSON output to test NUI behavior.

Instructions

Evaluate a JavaScript expression in a resource's NUI page (awaits promises, returns JSON)

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>",
      "expression": "<expression>"
    },
    "name": "nui_eval"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYes
expressionYes

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 flag destructiveHint=true and readOnlyHint=false, so the agent is warned this is not a safe read. The description adds genuinely useful behavior beyond that: it awaits promises and returns JSON, telling the agent how async results arrive. It does not warn that arbitrary JS execution can mutate page/app state, nor what happens on evaluation errors.

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 the key verb first and the async/return behavior in a tight parenthetical. No filler, though the brevity comes partly at the cost of missing operational detail.

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 that executes arbitrary code with destructiveHint=true and no output schema, the description is thin: no statement of execution context, permissions, error behavior, or what the JSON return looks like. It covers only the mechanics of evaluation and return type.

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 both parameters and does not. "expression" is loosely implied by the verb, but the resource parameter (which resource's NUI page, format constrained by the pattern) and the 16000-character expression limit are never mentioned.

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: "Evaluate a JavaScript expression in a resource's NUI page." The NUI-page framing implicitly separates it from lua_eval (server-side) and from nui_act/nui_snapshot, though no sibling is named explicitly.

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 or when-not-to-use guidance and no mention of alternatives such as lua_eval or nui_act. The only hint at appropriate usage is the implied NUI scope in the noun phrase, which an agent must infer.

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