Skip to main content
Glama
Sign In

GripForge

by io.github.gripforgeai
OverviewDiscussionsAdmin

Generate motions from text

gripforge_motion_generate

Custom animations generated from text with NVIDIA Kimodo on GripForge's GPU, retargeted onto a rigged Library character (or the UAL mannequin): spell casts, signature attacks, emotes, anything the standard clip pack (gripforge_animate) lacks. Kit mode turns a MOBA hero concept's basic attack and Q/W/E/R into clips in one call. Call stage=plan first (free) and show the prompts and price (1 credit per clip); stage=build queues a durable job — poll gripforge_generation_read with job_id (a cold GPU takes a few minutes). The result is a kind=animation Library item, one clip per prompt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gripforge_motion_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
stageNoplan (default, free): the clips that would be made and their price. build: queue the GPU job.
promptsNoFree clips, 1 to 12. Give either prompts or hero_concept_id.
character_idNoRigged Library character or enemy to retarget onto. Default: the UAL mannequin (any humanoid can reuse the clips later).
workspace_idNo
hero_concept_idNoKit mode: a hero concept with an ability kit (gripforge_game_concepts with hero_kits). Its basic attack and Q/W/E/R casts become one clip each, from the kit's "animation" lines.
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare the safety profile (not read-only, open world, not idempotent, non-destructive), and the description goes well beyond them: cost of 1 credit per clip, that build queues a durable job, cold-GPU latency of a few minutes, the polling target, and the result type (kind=animation Library item, one clip per prompt). This is unusually rich operational context.

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?

It is dense and front-loads the core capability, then layers the workflow and cost. Every sentence carries information, though the paragraph is packed enough that the plan-first instruction could be surfaced more prominently.

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 7-parameter generative tool with no output schema, the description covers input branching (prompts vs hero_concept_id), the staged workflow, pricing, async polling, and return format. Only idempotency and workspace scoping are left entirely to the schema.

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 57%, so the description must add meaning, and it does for the important parameters: stage plan/build semantics, prompts vs hero_concept_id exclusivity, character_id default (UAL mannequin), and kit-mode behavior. It omits workspace_id and idempotency_key semantics, but the meaningful parameters are covered.

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?

The description states a specific verb+resource ('custom animations generated from text') and explicitly frames its scope against siblings: it produces clips the standard pack (gripforge_animate) lacks, and it names the retarget target (rigged Library character or UAL mannequin). An agent can distinguish this from gripforge_animate and gripforge_weapon_motion without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit workflow guidance: 'Call stage=plan first (free)' before stage=build, names the polling sibling gripforge_generation_read with job_id, and explains kit mode as an alternative input path. When-to-use, prerequisites, and the follow-up tool are all present.

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