Skip to main content
Glama
Sign In
Anam MCP Server

Anam MCP Server

Official
by anam-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_avatar

Retrieve avatar details by providing the avatar's unique ID. This action fetches avatar information for Anam AI personas.

Instructions

Get details of a specific avatar by ID.

Args: avatar_id: The UUID of the avatar to retrieve

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": {
      "avatar_id": "<avatar_id>"
    },
    "name": "get_avatar"
  }
}

Input Schema

NameRequiredDescriptionDefault
avatar_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior but only states 'Get details' and parameter info. It does not explicitly confirm read-only nature, mention required permissions, or describe side effects. The return format is also not mentioned.

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 brief at one sentence plus an Args section. It is well-structured and avoids fluff, though the Args list duplicates schema information, which could be considered redundant but not harmful.

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 simple tool with one required parameter and an output schema, the description is adequate but leaves gaps. It does not explain what the output contains or any usage constraints, though the output schema partially compensates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, and the description only adds 'The UUID of the avatar to retrieve', which minimally clarifies the parameter beyond the schema's type and title. It could include format constraints or examples.

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 'Get details of a specific avatar by ID' with a specific verb and resource. It distinguishes itself from sibling tools like 'list_avatars' and 'search_avatars' by focusing on a single avatar 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 is provided on when to use this tool versus alternatives such as 'list_avatars' for fetching all avatars or 'search_avatars' for filtering. The agent is left without context on selecting this tool.

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