Skip to main content
Glama
Sign In

GripForge

by io.github.gripforgeai
OverviewDiscussionsAdmin

Map in-game screenshot refs

gripforge_map_refs
Read-onlyIdempotent

Look up reference stills of a known map the user names (A, B, mid, catwalk, tunnels, spawn). Returns HTTPS URLs of their owner. Reference only — do not rehost, do not send to Meshy image-to-3d. Read materials then generate ORIGINAL locker props. live=true HEAD-checks links. 0 credits. Preview https://gripforge.ai/map-plan?prompt=bomb%20defusal

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_map_refs"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNoHEAD-check URLs (default false)
promptYese.g. "bomb defusal"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"e.g. \"dust2\""New value: +"e.g. \"bomb defusal\""
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the bar is lower; the description still adds cost ('0 credits'), the return shape ('HTTPS URLs of their owner'), and the live=true HEAD-check behavior. It doesn't cover rate limits or failure behavior, keeping it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a chain of short telegraphic clauses that jump between purpose, licensing constraints, workflow, parameter behavior, cost, and an unexplained preview URL. The content is mostly useful but not front-loaded cleanly, and the trailing 'Preview' link appears tangential.

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 read-only lookup with no output schema, the description covers what it returns, the cost, the live behavior, and the legal/workflow constraints. An agent has enough to call it correctly, though failure/empty-result behavior is unstated.

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%, so baseline is 3, but the description adds meaning beyond the schema: it clarifies the prompt accepts map location names (A, B, mid...) and explains that live=true performs HEAD-checks on links. This is a genuine elaboration over the schema's terse 'HEAD-check URLs'.

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 ('Look up') and resource ('reference stills of a known map'), with concrete examples of map locations (A, B, mid, catwalk, tunnels, spawn) that scope the domain. It does not name a sibling tool to differentiate against, so it stops short of a 5, but the intent is unambiguous.

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 when-not guidance ('Reference only — do not rehost, do not send to Meshy image-to-3d') and workflow placement ('Read materials then generate ORIGINAL locker props'). No sibling alternative is named explicitly, so it's a 4 rather than 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