Skip to main content
Glama

List characters

list_characters
Read-onlyIdempotent

List the bitHuman house characters that can speak. Each has an id (pass it as character to make_character_video or talk_to_character), a name, a short description, a picture URL and talk (true when talk_to_character is open for it). No arguments and read-only; one call per conversation is enough. Only these characters can speak: real people, photos and custom voices are not supported.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
charactersYes
make_your_own_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, and the description adds real value beyond them: the caching guidance ('one call per conversation is enough'), the meaning of the `talk` flag, and the hard limitation on non-house characters. Return-format detail is partly redundant with the output schema, keeping this below 5.

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?

Three compact sentences, front-loaded with the resource and its downstream use, followed by usage constraints and scope limits. Nothing is wasted, though the field enumeration overlaps with the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An agent knows what it gets, that it is safe to call repeatedly, when one call suffices, and which use cases are out of scope. With an output schema present and annotations covering safety, nothing material is missing.

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?

Zero parameters, so baseline is 4. The description still adds cross-tool semantics by noting the `id` must be passed as `character` to make_character_video or talk_to_character, which no schema field conveys.

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?

States a specific verb and resource ('List the bitHuman house characters that can speak') and immediately names the fields returned. It also distinguishes itself from the siblings by explaining how the `id` feeds make_character_video and talk_to_character.

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

Usage Guidelines4/5

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

Gives clear operational context: no arguments, read-only, one call per conversation suffices, and the scope exclusion that real people, photos and custom voices are not supported. It does not spell out an explicit conditional alternative, but the downstream routing to the two siblings is stated.

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