Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_particle_info

Retrieve configuration and status details for a particle node to inspect its settings and current state.

Instructions

Get configuration and status information about a particle node.

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": {
      "node_path": "<node_path>"
    },
    "name": "get_particle_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the particle node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden. 'Configuration and status information' hints at a read operation and rough return content, but it never states that the call is read-only, what permissions are needed, or what fields the response contains. For an unannotated tool this is thin behavioral disclosure.

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?

It is a single front-loaded sentence with no filler, which is appropriate for a simple getter. The brevity does come at the cost of some useful detail, but nothing is redundant.

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 one-parameter read tool, the schema covers the input and no output schema exists. Still, with zero annotations the description should explain what 'configuration and status information' actually includes and confirm the read-only nature to be fully complete.

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 coverage is 100% for the single required parameter, so the schema already documents node_path adequately. The description adds no format, path-syntax, or lookup details beyond what the schema provides, so the baseline of 3 applies.

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 uses a specific verb ('Get') and resource ('configuration and status information about a particle node'), making the tool's scope clear. However, it does not differentiate itself from sibling readers like get_node_properties, which could plausibly return overlapping data for the same node.

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?

There is no guidance on when to choose this tool over alternatives such as get_node_properties, nor any stated prerequisites or exclusions. The agent must infer the use case entirely from the tool name and one-line purpose.

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