Skip to main content
Glama
Sign In

GripForge

by io.github.gripforgeai
OverviewDiscussionsAdmin

gripforge_shield_export

gripforge_shield_export
Read-onlyIdempotent

ADMIN ONLY. Compile a shield recipe into reusable native source files for Godot 4, Unity or Unreal 5, using the same geometry and shader functions. Returns files keyed by relative path plus install instructions. Write ALL files into a dedicated directory; never overwrite an existing modified package without checking. Includes enable/hit/shatter runtime; no mannequin or preview environment. Native builds require target-engine verification; source export is not visual certification.

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": {
      "engine": "<engine>"
    },
    "name": "gripforge_shield_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
configNo
engineYes
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / engine / enum
      Previous value: -[
-  "threejs",
-  "godot",
-  "unity",
-  "unreal"
-]New value: +[
+  "godot",
+  "unity",
+  "unreal"
+]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior; the description adds admin requirement, return format, runtime inclusions/exclusions, and verification caveats. The 'write ALL files' line reads as caller-side instruction rather than a claim that the tool mutates state, so it does not contradict readOnlyHint.

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?

Front-loads ADMIN ONLY and stays dense with useful caveats; there is no obvious filler. Some sentences pack multiple constraints together, but every clause adds operational value.

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?

Provides return format and important scope/caveat information despite having no output schema, and annotations cover safety. But for a complex nested-config export, it leaves config field meanings and workspace_id behavior undocumented, so an agent still lacks call-critical detail.

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%, and the nested config object contains many fields (seed, color, style, radius, etc.) with no descriptions. The description loosely maps the engine targets to 'engine' but does not explain config fields or workspace_id, so it fails to compensate for the coverage gap.

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?

States a specific verb ('compile') and resource ('shield recipe') into native source files for three named engines, plus the return shape. This clearly distinguishes it from preview/VFX-style siblings by its export-to-source focus.

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?

Marks ADMIN ONLY and gives operational cautions (dedicated directory, don't overwrite modified packages, verify native builds), which sets useful context. However it never names a sibling alternative or states the precise condition for choosing export over shield_vfx or other preview/generation tools.

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