Skip to main content
Glama
Sign In

GripForge

by io.github.gripforgeai
OverviewDiscussionsAdmin

HUD webfont + rank copy

gripforge_font
Read-onlyIdempotent

Google-font CSS + exact HUD copy for a game look (stylish action: Cinzel D–SSS, kart: Teko, tactical FPS: Barlow Condensed). Put letters in HTML/Text nodes. Do NOT rasterize ranks, km/h, or HUD numbers with an image model. 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": {
      "prompt": "<prompt>"
    },
    "name": "gripforge_font"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYese.g. "stylish gothic action"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"e.g. \"devil may cry like\""New value: +"e.g. \"stylish gothic action\""
  2. Changed1 schema field changed
    • removedInput schema / properties / look
      Removed value: -{
-  "description": "Rendering look, separate from the game style: stylized (neutral) | painted | toon | anime | realistic | lowpoly | pixel. Old values (handpainted, cartoon, low_poly…) are read as aliases. Omit for the style default.",
-  "enum": [
-    "stylized",
-    "painted",
-    "toon",
-    "anime",
-    "realistic",
-    "lowpoly",
-    "pixel"
-  ],
-  "type": "string"
-}
  3. Changed1 schema field changed
    • addedInput schema / properties / look
      Added value: +{
+  "description": "Rendering look, separate from the game style: stylized (neutral) | painted | toon | anime | realistic | lowpoly | pixel. Old values (handpainted, cartoon, low_poly…) are read as aliases. Omit for the style default.",
+  "enum": [
+    "stylized",
+    "painted",
+    "toon",
+    "anime",
+    "realistic",
+    "lowpoly",
+    "pixel"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the bar is lower; the description adds genuinely new context: the output form (CSS + copy) and the cost profile ('0 credits'). It does not describe the exact return shape, but the cost and non-rasterization guidance are useful operational detail beyond the annotations.

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 short sentences, front-loaded with the deliverable, then the placement rule and the negative constraint. The parenthetical font mapping is dense but earns its space by clarifying input vocabulary; nothing is redundant.

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 one-parameter, read-only, zero-cost lookup tool with full schema coverage and no output schema, the description covers purpose, correct usage location, a critical exclusion, and cost. The only omission is the precise response structure, which is minor here.

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 100% and the single 'prompt' parameter already carries an example, so baseline is 3. The description adds interpretable meaning by showing which look keywords map to which fonts, effectively teaching the agent what to put in the prompt.

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 deliverable — Google-font CSS plus exact HUD copy — and illustrates it with genre-to-font mappings (Cinzel for stylish action, Teko for kart, Barlow Condensed for tactical FPS). That is far more concrete than the name alone, though it does not explicitly contrast itself with nearby siblings such as gripforge_hud, gripforge_hud_bar, or gripforge_style.

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 both positive routing (use for HUD/rank text placed in HTML/Text nodes) and explicit exclusion (do NOT rasterize ranks, km/h, or HUD numbers with an image model), which steers the agent away from image-generation tools. The alternative is described by category rather than by named sibling tool, 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