Skip to main content
Glama
Sign In
Catalyst MCP for FiveM

Catalyst MCP for FiveM

by Geckomacabre
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ptfx_vanilla_search

Read-only

Search vanilla GTA V particle effects for FiveM by effect, asset, or texture keywords, returning matching effects, assets, loop data, textures, and cached .ypt files.

Instructions

Find vanilla effects by words in the effect, asset or texture names, e.g. 'confetti', 'firework burst', 'spark', 'flame'. Returns asset, effect, loops, textures and the cached .ypt.

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": {
      "query": "<query>"
    },
    "name": "ptfx_vanilla_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the return shape (asset, effect, loops, textures, cached .ypt), which is genuinely useful since there is no output schema, but it says nothing about match semantics (substring vs fuzzy, case sensitivity) or how the cache interacts with results.

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?

Two tight sentences: the search scope and examples come first, the return payload second. No filler, no restatement of the tool name.

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 two-parameter read-only search this is close, since query semantics and return contents are both covered without an output schema. The unexplained limit parameter and absent matching/ordering behavior are the remaining gaps an agent would want before calling it.

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 0%, so the description must carry the load. It does explain 'query' well via the name-matching scope and examples, but 'limit' is completely unexplained — including its odd negative minimum — leaving one of two parameters undocumented anywhere.

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 ('Find vanilla effects') and narrows the matching surface to words in effect, asset, or texture names, with concrete example queries. This is enough to tell it apart from a by-name fetch or a full index, though the description never explicitly contrasts those siblings.

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?

Usage is implied: give it words like 'confetti' or 'spark'. There is no explicit when-to-use/when-not, and no routing advice toward ptfx_vanilla_get or ptfx_vanilla_index for exact-name lookups or full listings, so the agent must infer the boundary.

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