posecode
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| posecode_authoring_guideA | Return the guide that teaches the Posecode (.posecode) language: grammar, joints, actions, and an example. Read this before writing a movement. |
| validate_posecodeA | Parse a .posecode document and return any errors plus configured range-of-motion (ROM) clamps. Use this to check the source before showing it to a user; a clean result is not a clinical safety assessment. |
| render_posecodeA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The guide tool is clearly distinct, and render_posecode versus validate_posecode are separated by output: a permalink versus errors and ROM clamps. There is minor overlap because render_posecode also says it validates, but the descriptions route agents to the appropriate tool.
render_posecode and validate_posecode follow a verb_noun pattern, but posecode_authoring_guide breaks the pattern as a noun phrase. The shared posecode_ prefix helps, but the inconsistent structure across only three tools makes the set feel mixed.
Three tools is a tight, well-scoped set for a language authoring server: learn the format, validate the source, and render a viewable animation. Each tool earns its place and the count feels appropriate for the narrow domain.
The tools cover the full authoring workflow, from reading the grammar guide to checking errors and producing a shareable 3D animation. For the stated purpose, there are no obvious gaps or dead ends.