Skip to main content
Glama
Sign In
Gear

Gear

by wvfp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

script-modify

Add functions, variables, or signals to existing GDScript scripts without manual editing. Supports annotations and type hints.

Instructions

[compact alias of modify_script] Adds functions, variables, or signals to an existing GDScript. Use to extend scripts without manual editing. Supports @export, @onready annotations and type hints.

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": {
      "projectPath": "<projectPath>",
      "scriptPath": "<scriptPath>",
      "modifications": "<modifications>"
    },
    "name": "script-modify"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesAbsolute path to project directory containing project.godot. Use the same path across all tool calls in a workflow.
scriptPathYesPath to existing .gd file relative to project (e.g., "scripts/player.gd")
modificationsYesArray of modifications to apply
reasonNoOptional reason/context for this change. Displayed in visualizer audit timeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden. It states the tool adds items to existing scripts but does not disclose important behavioral traits such as conflict handling (e.g., duplicate names), whether modifications are applied atomically, or the success/failure response. This is insufficient for a mutation tool.

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 sentence that immediately conveys the core purpose and key features. Every word adds value, and it is effectively front-loaded. No unnecessary information is present.

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 tool's complexity (nested array of modifications) and absence of output schema or annotations, the description is too brief. It does not explain return values, error conditions, or ordering of modifications. The schema covers parameters well, but behavioral context is lacking.

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 100%, so baseline is 3. The description adds context about '@export' and '@onready' annotations, which relate to the 'isExport' and 'isOnready' properties. However, it does not add meaning for 'projectPath', 'scriptPath', or 'reason' beyond schema details. Overall, it provides marginal added value.

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 clearly states the tool adds functions, variables, or signals to an existing GDScript, using a specific verb and resource. It distinguishes itself from sibling tools like script-create (which creates new scripts) by focusing on extending existing scripts. The mention of '@export', '@onready', and type hints adds specificity.

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?

The description says 'Use to extend scripts without manual editing,' providing a clear usage context. However, it does not explicitly state when not to use it or mention alternatives like script-create for creating entire scripts. The guidance is implied but not complete.

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