GripForge

Modify a selection with AI

gripforge_scene_modify

Queue a scoped edit of saved scene nodes or a region. The server derives the allowed scope and preserves locks, gameplay zones, outside geometry and the last validated revision. Blender may fabricate missing assets. The result is a proposal requiring explicit application, never a silently replaced map.

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": {
      "id": "<id>",
      "expectedRevision": "<expectedRevision>",
      "nodeIds": "<nodeIds>",
      "prompt": "<prompt>"
    },
    "name": "gripforge_scene_modify"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`prompt`	Yes
`nodeIds`	Yes
`workspace_id`	No	Workspace authorized by the current key. Returned scene links open this workspace.
`blendDistance`	No
`idempotency_key`	No
`expectedRevision`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 20, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations are minimal and non-contradictory, so the description carries the behavioral burden. It discloses queued execution, server-derived scope, preservation guarantees, the possible Blender side effect of fabricating missing assets, and the explicit proposal/application contract that prevents silent replacement.

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?

Four front-loaded sentences cover action, scope, safety preservation, a side-effect warning, and the proposal contract without filler. Each sentence earns its place and the structure supports quick agent scanning.

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?

The safety and lifecycle behavior are well described, but the definition is incomplete for a 7-parameter tool with no output schema: it does not explain how the proposal is returned or retrieved, how a region is expressed, or what blendDistance controls. These gaps matter for correct invocation and follow-up.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, and the description does not compensate for the undocumented parameters. It only obliquely hints at expectedRevision through last validated revision and at nodes/region selection, while leaving idempotency_key, blendDistance, id, prompt, and nodeIds semantics mostly to inference.

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 opens with a specific verb and resource: Queue a scoped edit of saved scene nodes or a region. It further distinguishes itself from direct write/apply siblings by clarifying that the result is a proposal requiring explicit application and never a silently replaced map.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when to use the tool: the server derives allowed scope, preserves protected scene elements and the last validated revision, and returns a proposal rather than silently replacing the map. It does not explicitly name alternative scene-write or apply tools, but the proposal/apply contract makes the intended usage clear.

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

All GripForge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.