Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_eqs_test

Idempotent

Add a test class to an EQS query option idempotently, with undo support and optional option targeting.

Instructions

Add a test of test_class to an option of a UEnvQuery asset, after the option's existing tests. Idempotent per class: if the option already has a test of that class, that one is returned (already_existed=true) and nothing is added, so an option holds at most one test per class. option_index names an existing option, or equals the option count to append one new empty option; a negative option_index, or one past the option count, is an error checked before anything changes. Undoable as one editor transaction; marks the asset dirty without saving (save_asset). Valid classes: list_eqs_test_types; configure the test with set_eqs_test_scoring; remove_eqs_test is the inverse.

Returns: { query_path, option_index, test_class, test_name, test_index, test_count, already_existed } — idempotent by test class within the option

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
query_pathYes/Game/... path to the UEnvQuery asset (required)
test_classYesTest class name (e.g. "Distance", "Trace", "Pathfinding", "Dot") or full path
option_indexNoOptional option index to target (default 0); the current option count appends a new option, a larger index is refused

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • changedInput schema / properties / option_index / description
      Previous value: -"Optional option index to target (default 0; created if missing)"New value: +"Optional option index to target (default 0); the current option count appends a new option, a larger index is refused"
  2. First observedv1.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds substantial context beyond them: the already_existed=true short-circuit, that errors are validated before any change, that the edit is undoable as a single editor transaction, and that the asset is marked dirty without being saved. This is strong behavioral disclosure for a mutation tool.

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?

Dense but well-organized and front-loaded, with the core action first and constraints/tooling after. Every clause carries information, though the density is high enough that it reads more like a spec than a short blurb.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description supplies the exact return fields and semantics (already_existed, test_index/count). For a mutation tool with clear annotations, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description nonetheless adds meaning beyond the schema for option_index: equals the option count appends, and negative or past-count values are refused.

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

Purpose5/5

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

States a specific verb and resource ('Add a test of test_class to an option of a UEnvQuery asset') with exact placement scope ('after the option's existing tests'). It clearly distinguishes itself from the EQS siblings (add_eqs_option, add_eqs_generator) by naming the inverse and related tools.

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

Usage Guidelines5/5

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

Explicitly routes the agent: list_eqs_test_types for valid classes, set_eqs_test_scoring to configure, remove_eqs_test as the inverse. It also states the idempotency rule and the exact condition under which option_index appends versus errors.

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