Anam MCP Server

Official

by anam-org

Overview Schema Source Related Servers Discussions Admin

Python

Remote

create_avatar

Generate a custom avatar by providing a display name and an image URL. Available for enterprise and pro plans.

Instructions

Create a custom avatar from an image URL.

Note: This feature is only available for enterprise and pro plans.

Args: name: Display name for the avatar image_url: URL of the image to use

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": {
      "name": "<name>",
      "image_url": "<image_url>"
    },
    "name": "create_avatar"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`image_url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.13May 29, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description adds a plan restriction note but otherwise only repeats the basic action. With no annotations, more behavioral context (e.g., required permissions, side effects, rate limits) would improve transparency, though the core operation is straightforward.

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?

The description is concise, using a note for important context and a bullet list for parameters. It avoids redundancy and is well-organized, though the structure could be slightly more formal.

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?

Given the presence of an output schema and the simple nature of the tool, the description is reasonably complete. It covers the purpose, plan limitation, and parameters. It could mention return value or error cases, but these are not critical for understanding.

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?

The description provides brief but clear explanations for both parameters ('name: Display name for the avatar', 'image_url: URL of the image to use'), which compensates for the 0% schema coverage. It adds meaning beyond the raw schema properties, though constraints like URL format or name length are missing.

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 description clearly states the tool's function: creating a custom avatar from an image URL. It is distinct from sibling tools like delete_avatar or update_avatar, leaving no ambiguity about the primary action.

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

Usage Guidelines2/5

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

The description lacks guidance on when to use this tool versus alternatives. It only mentions a plan restriction (enterprise/pro) but does not compare with other avatar-related tools like add_avatar_to_meeting or update_avatar, leaving the agent to infer context.

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

Deploy Server