Skip to main content
Glama
Sign In
Anam MCP Server

Anam MCP Server

Official
by anam-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_avatars

Retrieve a paginated list of AI avatars with IDs, names, variants, and type (stock or custom). Use page and per_page parameters to control results.

Instructions

List all available avatars.

Returns a formatted summary of avatars with IDs, names, variants, and type (stock/custom).

Args: page: Page number (default: 1) per_page: Items per page (default: 100)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_avatars"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses pagination behavior and return format but lacks details on permissions, rate limits, or whether results are global or user-scoped. The described defaults differ from schema defaults (null vs 1/100), which may confuse an agent.

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 succinct with a purpose sentence and parameter details. It is front-loaded and easy to parse. Could be slightly more concise but is well-structured.

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 complexity (paginated list) and presence of an output schema, the description adequately covers the tool's function and parameters. It differentiates from siblings and mentions return fields, but omits potential constraints like maximum per_page.

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 0%, but the description provides defaults and meaning for both parameters ('Page number (default: 1)', 'Items per page (default: 100)'). This adds value beyond the schema, though the discrepancy with schema defaults (null) is a minor issue.

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 lists all available avatars and mentions the return format (IDs, names, variants, type). It differentiates from siblings like 'search_avatars' and 'get_avatar' by implying a full list rather than a filtered search or single retrieval.

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?

No guidance on when to use this tool versus alternatives like 'search_avatars'. The description implies a full listing but does not explicitly state the context or exclusions.

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