Skip to main content
Glama
Sign In
Anam MCP Server

Anam MCP Server

Official
by anam-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_persona

Retrieves detailed information about an AI persona using its unique ID. Provides persona details for integration with Anam AI.

Instructions

Get details of a specific persona by ID.

Args: persona_id: The UUID of the persona 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": {
      "persona_id": "<persona_id>"
    },
    "name": "get_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
persona_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, so description must cover behavior. It only says 'Get details' with no mention of error handling (missing ID), permissions, or idempotency, leaving significant gaps.

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?

Two short sentences, front-loaded with purpose, no unnecessary words.

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?

Tool is simple with one param and output schema exists. Description is minimally adequate but lacks info on return value, errors, or edge cases.

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 has 0% description coverage, but description adds 'The UUID of the persona to retrieve', clarifying format (UUID) beyond schema's plain 'string' type.

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?

Description clearly states 'Get details of a specific persona by ID', specifying verb (get) and resource (persona by ID), distinct from siblings like list_personas.

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?

No explicit when-to-use or alternatives mentioned. Usage is implied (when you have an ID), but no guidance against using for listing or comparison with list_personas.

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