Skip to main content
Glama

Save a rigged model as a living, persistent agent body

create_agent_persona

Turn a generated GLB into a NAMED, persistent agent body: a "persona" the assistant reuses across turns and across sessions. The model is copied into durable storage so the body survives the source URL expiring, then registered under a stable persona_id. The returned view renders the LIVING body inline: it idles between turns, and persona_say makes it lip-sync and emote a reply. The persona_id is the handle: keep it and pass it to get_agent_persona or persona_say later to bring the exact same body back. Use this once a rigged model should become a recurring character the assistant speaks through. Saving a persona needs a free three.ws account (OAuth sign-in or an API key as the bearer); get_agent_persona and persona_say work without one.

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": {
      "glb_url": "<glb_url>",
      "name": "<name>"
    },
    "name": "create_agent_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA display name for the persona, 1–80 characters.
voiceNoOptional voice name to speak with (used for audio-driven lip-sync when available).
glb_urlYesPublic https URL of the rigged GLB to embody (e.g. from forge_avatar).
source_promptNoOptional: the prompt that generated this body, kept as provenance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses real behavior: the GLB is copied into durable storage so the body survives source-URL expiry, and it is registered under a stable persona_id. It also discloses the auth requirement, which annotations do not convey. It stops short of saying what happens if the same name is saved twice or whether saving consumes quota, which matters given idempotentHint=false.

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?

Structure is front-loaded: capability first, then persistence mechanics, then the handle, then auth. It is slightly longer than needed and the all-caps emphasis (LIVING, NAMED) is stylistic noise, but each sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by describing what comes back: an inline rendered living body that idles and lip-syncs via persona_say, plus the persona_id handle. Persistence, reuse, and auth prerequisites are all covered, leaving nothing essential unstated for a four-parameter creation tool.

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%, so name, voice, glb_url, and source_prompt are already documented; the description adds only light reinforcement (voice used for lip-sync, glb_url typically from forge_avatar appears only in schema). The persona_id it explains at length is a return value, not an input parameter.

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 opening sentence names a specific verb and resource — turning a generated GLB into a named, persistent agent body — and immediately frames the output as a reusable persona. It clearly separates itself from siblings by noting that get_agent_persona and persona_say are the later steps for consuming the created persona_id.

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 states the trigger condition explicitly ('Use this once a rigged model should become a recurring character the assistant speaks through') and names the downstream alternatives (get_agent_persona, persona_say) along with the crucial difference that those work without an account. Prerequisite auth (free three.ws account via OAuth or API key bearer) is stated up front.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.