Skip to main content
Glama

List Characters

list_characters
Read-onlyIdempotent

[read] The caller's characters, newest first: character_uuid, name, status (DRAFT | READY), style, purpose, type, language (character_language), options (niche, usp, format, money, look, eye/hair/skin/body), character_bio (the profile bio per network) and character_note (the private note), character_main_asset_id (the picture shown when the character is picked in images and videos), character_reference_asset_id (the picture the stages draw from; the main one when empty) and the character_assets made so far (each with asset_id, stage, variant, url). Only a READY character can be used in a picture or a video.

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_characters"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context on top: results are scoped to the caller, sorted newest first, each character is qualified by DRAFT vs READY status with the constraint that only READY characters are usable in images or videos, and it explains the fallback rule for character_reference_asset_id when empty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, and every element listed earns its place given there is no output schema. However, the return-value enumeration is delivered as a single ~100-word run-on sentence with deeply nested parentheses, which makes it hard to scan and pushes the important READY constraint into a trailing aside.

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?

Because no output schema exists, the field-by-field return description carries real weight and covers most of what an agent needs. The remaining gaps are pagination mechanics and whether a total count is returned, which matter for a list endpoint with page/per_page.

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 two parameters (page, per_page) at 0% description coverage, and the description never mentions pagination, page size limits, or how paging interacts with the 'newest first' ordering. With no schema descriptions, this is exactly the case where the description needed to compensate, and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with '[read] The caller's characters, newest first', which names the resource, the scope (caller-owned only) and the ordering, and the plural framing distinguishes it from the sibling get_character. It never explicitly contrasts itself with get_character or list_character_prompts, so the differentiation is inferable rather than stated.

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?

Usage is only implied: the '[read]' prefix and the caller-scoped framing tell the agent this is a safe browsing call. There is no explicit guidance on when to prefer this over get_character or list_character_prompts, and no mention of iterating pages when results are truncated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources