Skip to main content
Glama
Sign In
Catalyst MCP for FiveM

Catalyst MCP for FiveM

by Geckomacabre
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

catalyst_open

Opens a .ypt particle file in Cfx.re's Catalyst editor for preview, just like double-clicking it, and brings the editor window to the front.

Instructions

Open a .ypt in Catalyst (Cfx.re's particle editor), if it is installed, to preview it - the same as double-clicking it. Uses Catalyst's own file association (--import). Catalyst opens in front of other windows.

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": {
      "ypt": "<ypt>"
    },
    "name": "catalyst_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
yptYesabsolute path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description goes further by disclosing the installation prerequisite, the mechanism (Catalyst's own file association via --import), and the side effect that Catalyst takes foreground focus. It does not say how failure looks when Catalyst is absent or whether the call waits for the app, which keeps it from a 5.

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?

Three short clauses, front-loaded with the action and file type; the usage constraint, the mechanism, and the window-focus caveat each add distinct information with no filler.

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

Completeness4/5

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

For a one-parameter launcher with no output schema, the definition covers the precondition, the invocation mechanism, and the visible side effect. Only error behavior and blocking semantics are unaddressed, which are minor for a fire-and-launch tool.

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 100% and the single parameter is already documented as an absolute path, so the baseline is 3. The description adds real meaning by constraining the file type to .ypt and tying it to Catalyst's import path, which the schema does not state.

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 ('Open') and resource (a .ypt particle file) plus the target application, defined inline as Cfx.re's particle editor. The 'same as double-clicking it' analogy pins down the behavior precisely, and nothing among the ptfx_* siblings does this external-launch job.

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

Usage Guidelines4/5

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

The purpose ('to preview it') makes the when-to-use condition clear, and 'if it is installed' states a precondition an agent must check. It stops short of naming exclusions or pointing at a sibling when previewing is not wanted, so it is clear context rather than full routing guidance.

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