Skip to main content
Glama
Sign In
Godot MCP

Godot MCP

by KeeVeeG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_particle_velocity_curve

Define particle velocity over time by specifying curve points with offset and value pairs.

Instructions

Set a velocity curve for a particle system

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": {
      "path": "<path>",
      "curve": "<curve>"
    },
    "name": "set_particle_velocity_curve"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesParticle node path
curveYesCurve points

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states 'set' which implies mutation but does not describe side effects, error conditions, whether it replaces or appends to existing curves, or if any permissions are needed.

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 concise sentence with no unnecessary words. It is front-loaded with the core action and resource.

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?

The tool lacks output schema and annotations. The description does not mention what happens after setting the curve (e.g., whether it returns success, confirmation, or errors). For a mutation tool, more context on behavior and expected outcomes is needed.

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?

The input schema covers 100% of parameters with descriptions, so the schema already documents the parameters. The tool description adds no additional semantic meaning beyond restating the tool's purpose; it does not explain how the curve array maps to particle behavior or what valid values mean.

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 clearly states the tool sets a velocity curve for a particle system, using a specific verb and resource. It is unambiguous but does not explicitly distinguish from sibling tools like set_particle_color_gradient or set_particle_material, which operate on different aspects of particles.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as requiring an existing particle node, or comparative context with other particle setting tools.

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