Skip to main content
Glama
Sign In
ultimate-construct3-mcp

ultimate-construct3-mcp

by nahuelgallo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_ace_reference

Fetches the Actions, Conditions, and Expressions (ACE) reference for a Construct 3 plugin or behavior by slug, enabling lookup of available ACEs and language-specific documentation.

Instructions

Get the Actions, Conditions, and Expressions (ACE) reference for a Construct 3 plugin or behavior.

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": {
      "plugin": "<plugin>"
    },
    "name": "get_ace_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage code (default: en)
pluginYesPlugin or behavior slug (e.g. 'sprite', 'platform', 'tween')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only lookup but does not state whether the reference is static or version-specific, what happens if an unknown plugin is passed, or what form the response takes.

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?

The description is a single efficient sentence with the key resource and scope front-loaded. Every part of the sentence earns its place.

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

Completeness3/5

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

For a simple two-parameter lookup tool with no output schema, the description covers the basic purpose but leaves behavioral and return-format gaps. Given the absence of annotations, it should say more about what the agent will receive and how errors are handled.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented in the schema. The description adds only the expansion of the ACE acronym and confirms that the plugin parameter accepts either a plugin or behavior slug, which is a marginal addition over the schema.

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 states a specific verb and resource: retrieving the Actions, Conditions, and Expressions reference for a named Construct 3 plugin or behavior. It is clear what the tool returns, though it does not explicitly differentiate itself from sibling tools like get_doc or search_docs.

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 usage is implied: use this when you need ACE details for a specific plugin or behavior. However, the description does not say when to prefer this over search_docs or get_doc, nor does it mention prerequisites or exclusions.

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