Skip to main content
Glama
Sign In

GripForge

by io.github.gripforgeai
OverviewDiscussionsAdmin

Studios · mesh passport

gripforge_mesh_passport

Read or correct the passport of a locker mesh (size, orientation, reference skeleton, colliders). manual merges a human correction (it always wins and survives regeneration); clear removes one. Measurements themselves come from gripforge_tool_run tool=passport.

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": {
      "item_id": "<item_id>"
    },
    "name": "gripforge_mesh_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoRemove one correction (orientation, joints.elbow.L, fits.helm) or "*" for all.
manualNoPartial PassportManual to MERGE (e.g. {"orientation":{"up":[0,1,0],"front":[0,0,1],"toCanonical":[0,0,0,1],"confidence":1,"source":"manual"}}). Omit to read.
item_idYes
workspace_idNoWorkspace id (defaults to the key’s workspace).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the manual correction 'always wins and survives regeneration', which tells the agent the persistence semantics of a write. It omits auth/permission needs and response shape.

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?

Three tight sentences, front-loaded with the read/correct purpose before the parameter semantics. The final sentence about measurements earns its place by redirecting the agent to gripforge_tool_run rather than being filler.

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 mutating tool with nested objects and no output schema, the description covers the operation, the correction-overlay model, and where measurement data actually lives. It leaves the read return value and permission requirements implicit, which keeps it from being fully complete.

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

Parameters4/5

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

Schema coverage is 75%, so the schema documents most parameters (clear, manual, workspace_id), but the description still adds meaning beyond it: it explains that 'manual' is a merge whose value wins and survives regeneration, and that 'clear' removes a single named correction. That persistence guarantee is not in the schema text.

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?

States a specific verb pair and resource: 'Read or correct the passport of a locker mesh', then enumerates what the passport covers (size, orientation, reference skeleton, colliders). It also carves out a boundary by noting measurements come from gripforge_tool_run tool=passport, though it does not contrast with the read-only sibling path as sharply as a 5 would.

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 context for each mode – 'manual' merges a human correction that always wins and survives regeneration, 'clear' removes one – and routes measurement lookups to gripforge_tool_run tool=passport. No explicit when-not or prerequisite conditions are stated, so it stops short of 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