Skip to main content
Glama

Render a Posecode movement to a link

render_posecode

Validate a .posecode document and produce a permalink that animates it as a 3D figure for viewing the movement in the Posecode playground.

Instructions

Validate a .posecode document and return a permalink that animates it as a 3D figure in the Posecode playground. Give the link to the user to view the movement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesThe full .posecode document text
Behavior4/5

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

No annotations provided, but description transparently states validation and permalink generation. Missing details on potential errors or permissions, but no indication of hidden behavior.

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

Conciseness5/5

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

Two short sentences: first describes function, second provides user instruction. No superfluous words.

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?

Adequately covers purpose and output for a simple tool with one parameter and no output schema. Could mention error conditions or output format (URL) but not necessary.

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

Parameters3/5

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

Schema coverage is 100%, and parameter description in schema matches description text. The tool description adds no additional semantics beyond the schema.

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?

Clearly states it validates a .posecode document and returns a permalink for 3D animation, effectively distinguishing from sibling tools like validate_posecode which only validates.

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?

Implicitly indicates usage for creating shareable animations by telling to give link to user, but does not explicitly compare with sibling tools like validate_posecode or posecode_authoring_guide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/posecode-dev/posecode'

If you have feedback or need assistance with the MCP directory API, please join our Discord server