Skip to main content
Glama
Sign In

GripForge

by io.github.gripforgeai
OverviewDiscussionsAdmin

Creature rig · detect anatomy

gripforge_creature_analyze

Queue multiview mesh inspection and vision anatomy detection for an OWNED GLB. Detect actual body, legs, arms, claws, wings or tail without imposing a humanoid/eight-leg template. Returns a persistent job_id. Poll gripforge_generation_read with include_preview=true for the annotated views, editable profile and uncertainty flags. No rig mutation. 0 GripForge credits; configured server vision/Blender required.

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": {
      "source_id": "<source_id>"
    },
    "name": "gripforge_creature_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
nameNo
source_idYes
workspace_idNo
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "enemy",
-  "character"
-]New value: +[
+  "enemy",
+  "character",
+  "creatures"
+]
  2. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotation coverage exists (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds genuinely non-structured context: async job semantics ("persistent job_id"), cost ("0 GripForge credits"), prerequisites ("configured server vision/Blender required"), and a non-mutation guarantee. It does not explain the idempotency behavior implied by idempotentHint=false, leaving a small gap.

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 action is front-loaded in the first sentence and the sentences are dense with distinct information (scope, behavior, follow-up, cost, prerequisites). It runs slightly long, but each clause carries new content rather than restating the name.

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 an async, server-dependent tool with no output schema, the description covers the workflow loop and prerequisites reasonably well. However, with 5 undocumented parameters and no hint on what a completed job returns, it is only minimally adequate rather than complete.

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 0% across 5 parameters, so the description carries the full burden, yet it names none of them. source_id is only hinted at via "OWNED GLB"; kind, name, workspace_id and idempotency_key are not explained anywhere, so an agent gets no semantics for most inputs.

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 states a specific action (queue multiview mesh inspection + vision anatomy detection) on a specific resource (an OWNED GLB), and clarifies what it is not ("No rig mutation"). It also names the downstream sibling gripforge_generation_read, but does not distinguish itself from close siblings like gripforge_creature_rig or gripforge_inspect.

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?

There is useful implied context (owned GLB, configured server vision/Blender required) and a clear follow-up instruction to poll gripforge_generation_read, but no explicit statement of when to choose this over gripforge_creature_rig, gripforge_inspect, or the generation tools. Usage is implied rather than declared.

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