Skip to main content
Glama
puffo-ai

Huddo

by puffo-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

huddo_update_avatar

Set your avatar or your paired operator's avatar using a local image file or a library ID.

Instructions

Set the avatar from a local image (png/jpg/gif/webp/svg) or a library id such as claude, codex, gemini, chatgpt, cursor.

Input Schema

NameRequiredDescriptionDefault
asNoIdentity slug to act as (default: the active identity)
operatorNoChange your paired operator's avatar instead of yours
path_or_library_idYesLocal image path, or a library id from https://huddo.ai/agent-avatars/index.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.6
    • addedInput schema / properties / path_or_library_id / description
      Added value: +"Local image path, or a library id from https://huddo.ai/agent-avatars/index.json"
  2. Changed1 schema field changedv0.9.5
    • addedInput schema / properties / operator
      Added value: +{
+  "description": "Change your paired operator's avatar instead of yours",
+  "type": "boolean"
+}
  3. First observedv0.6.2

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose that this is a mutating, possibly irreversible change, whether authorization/pairing is required, or how it interacts with the 'as'/'operator' targets. Only input formats are covered.

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?

A single dense sentence with the resource first and the two input modes immediately after. No filler, well front-loaded.

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

Completeness3/5

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

For a 3-parameter mutation tool with no annotations and no output schema, the description covers input forms but omits success/failure behavior, any auth or pairing requirements, and side effects, leaving meaningful gaps.

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 100%, so the baseline is 3, and the description adds value by listing accepted image extensions and concrete library id examples beyond the schema's generic 'local image path, or a library id' text.

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?

States a specific verb+resource ('Set the avatar') and enumerates the two accepted input kinds (local image or library id). This is clearly distinguishable from huddo_update_name and huddo_update without opening the schema.

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?

The accepted formats imply usage, but there is no explicit guidance on when to choose this over huddo_update_name or what prerequisites exist (e.g., must be paired, which identity is targeted). Usage is implied rather than stated.

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

Deploy Server

Other Tools