Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

call_method

Destructive

Invoke a method on a resolved Godot object, passing typed positional arguments and receiving the result as JSON; invalid types or counts return an error instead of failing silently.

Instructions

Invoke a method on a resolved object. args = a positional array, coerced to the declared param types: vectors accept [x,y,z] / {"x":..} / "x y z", colors hex or [r,g,b,a], object params a node name/path or res:// path. set / set_deferred / set_indexed hold the value to the property's type, as set_property does. Wrong types or counts return an ERROR (never a silent no-op). Returns the result as JSON.

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": {
      "target": "<target>",
      "method": "<method>"
    },
    "name": "call_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
methodYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.1
  2. Removedv1.10.0
  3. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds meaningful behavioral detail beyond annotations: type coercion rules, the fact that wrong types or counts return an ERROR rather than silently no-op, and that results are returned as JSON.

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?

The description is front-loaded with purpose and then moves into parameter semantics and error/return behavior. It is dense but mostly efficient; the set/set_deferred/set_indexed sentence is somewhat niche but still relevant to argument handling.

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?

Given the lack of an output schema, the description usefully states that results are returned as JSON. However, for a generic method-invocation tool with required target and method parameters, it does not explain how targets are identified or what form method names should take, leaving a notable gap.

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 parameter meaning. It compensates well for the complex 'args' parameter with detailed coercion examples, but the required 'target' and 'method' parameters remain largely undefined beyond their names and the phrase 'resolved object'.

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?

The description uses a specific verb and resource: 'Invoke a method on a resolved object.' It also implicitly distinguishes this tool from property-setting siblings by noting how set/set_deferred/set_indexed behave relative to set_property.

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 explicit guidance on when to use this tool versus alternatives such as set_property, find_methods, or describe_object. The description explains argument coercion but does not say when this generic method invocation is appropriate or when another sibling should be chosen.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.