Skip to main content
Glama
Sign In

GripForge

by io.github.gripforgeai
OverviewDiscussionsAdmin

Derive a lighter version

gripforge_library_optimize

Derive a lighter version of a static model (prop, weapon, equipment, vehicle) for a target: decimated to triangles, textures bounded to texture px, saved as a NEW Library item linked to its master (meta.lod_of). The master is never changed — generate high once, derive mobile/desktop versions. Wheel pivots and nodes are kept. 0 credits.

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>",
      "triangles": "<triangles>"
    },
    "name": "gripforge_library_optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLibrary id of the master model (lib_…)
nameNo
errorNoLargest decimation error relative to the model size (default 0.005); far levels of detail use 0.02–0.08 to reach low counts
textureNoMax texture size in px (default 2048)
trianglesYesTarget triangles, e.g. 12000 for a mobile car, 40000 desktop

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / error
      Added value: +{
+  "description": "Largest decimation error relative to the model size (default 0.005); far levels of detail use 0.02–0.08 to reach low counts",
+  "maximum": 0.2,
+  "minimum": 0.001,
+  "type": "number"
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds real value on top: the output is a NEW item linked via meta.lod_of, the master is untouched, wheel pivots/nodes are preserved, and it costs 0 credits. It omits that repeated calls will accumulate duplicate derived items (consistent with idempotentHint=false), which is the one behavioral gap.

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 tight clauses, front-loaded with the core action, then scope, then invariants, then cost. No filler and no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation tool with no output schema, the description covers the essential behavior: what is produced (a new linked Library item), what is preserved (pivots, nodes), and what it costs. It does not state what identifier is returned for the new item, which is the only material 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 coverage is already 80%, so the schema documents id, name, error, texture, and triangles. The description restates only `triangles` and `texture` in narrative form and says nothing about `error` or `name`, so it adds little beyond the schema. Baseline 3 applies.

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?

Specific verb ('Derive a lighter version') plus the resource scope (static model: prop, weapon, equipment, vehicle) and the exact transformations applied (decimation to `triangles`, texture bounded to `texture` px, saved as a NEW Library item with meta.lod_of). An agent can distinguish this from generation siblings like gripforge_generate_vehicle without opening any schema.

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?

Gives clear workflow guidance — 'generate high once, derive mobile/desktop versions' — and states the invariant that the master is never changed. It does not name any alternative tool or state when-not-to-use (e.g., vs. gripforge_scene_optimize or gripforge_texture_prep), so it stops short of a 5.

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

All GripForge toolsInspect
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.

Resources