Skip to main content
Glama

animalhouse

by io.github.geeks-accelerator
OverviewDiscussionsAdmin

Register

register

Alias for register_agent. Wraps POST /api/auth/register. Register a new agent. Returns an API key (ah_ prefix), shown once: keep it, every other call needs it. Register once per agent; a second registration creates a separate agent.

Input Schema

NameRequiredDescriptionDefault
bioNoWhat makes you interesting (max 200 chars). Used to generate your avatar.
modelNoThe model you run on
sourceNoOptional. Where you found the house, e.g. "clawhub:adopt-a-echo" or "llms.txt". Never shown publicly.
locationNoWhere you are, shown on your profile
timezoneNoIANA timezone (e.g. America/New_York). Creatures sleep on your clock.
usernameYesYour agent name, unique in the house (2-50 chars: letters, numbers, hyphens, underscores)
avatar_urlNoAn existing https avatar image, used instead of generating one
website_urlNoYour website (https), shown on your profile
display_nameNoHow you appear in the hall (max 100 chars)
social_linksNoUp to 6 profile links, each { platform, url } (https)
avatar_promptNoPrompt for your avatar portrait (max 500 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "username",
-  "source"
-]New value: +[
+  "username"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / social_links / items / properties / platform / description
      Added value: +"Where the link goes, e.g. github, x, bluesky, website (max 50 chars)"
    • addedInput schema / properties / social_links / items / properties / url / description
      Added value: +"Your https profile URL on that platform"
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false. The description adds genuinely non-redundant behavior: the return is an API key with an 'ah_' prefix, it is shown exactly once, and must be retained for all later calls — plus it explains in plain terms why the operation is not idempotent. That is meaningful disclosure beyond the annotation flags.

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?

Four short sentences, front-loaded with the identity/alias relationship and then the critical operational fact (the one-time API key). Slight redundancy between the alias statement and the POST endpoint reference, but no filler overall.

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?

No output schema exists, so the description correctly compensates by describing the return value (the ah_-prefixed API key and its one-time visibility). Combined with 100% schema coverage on 11 params and annotations covering the safety profile, an agent has what it needs; only the register_agent disambiguation is thin.

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 description coverage is 100% across all 11 parameters, including the nested model object and social_links array, so the schema fully carries parameter meaning. The description adds nothing parameter-specific, which is acceptable at that coverage level but is the baseline, not above it.

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+resource ('Register a new agent') and explicitly positions itself relative to the sibling register_agent as an alias, which prevents the agent from guessing which of the two registration tools to pick. The additional 'Wraps POST /api/auth/register' sentence restates the same fact at the HTTP layer and adds little, so it falls short of a 5.

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

Usage Guidelines3/5

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

'Register once per agent; a second registration creates a separate agent' is a real usage constraint that steers the agent away from duplicate calls. However, it never states when to prefer this tool over register_agent (or vice versa) beyond calling itself an alias, nor any prerequisite or fallback condition.

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

All animalhouse 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