Digital Maker AI

list_characters

Read-onlyIdempotent

List the characters the user has saved, with their descriptions and the style preset each was made for. Use this when they mention a character by name, ask who they have saved, or before making a video that stars someone.

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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the read-only and idempotent annotations, the description discloses the user-saved scope and the metadata returned for each character. It does not mention ordering or empty-result behavior, but those are modest omissions for a zero-argument listing operation.

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-load the operation and result contents, then provide selection triggers. There is no filler or redundant restatement of the annotations.

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?

For a simple, zero-argument, read-only tool, the description supplies enough scope, output context, and usage guidance to select and invoke it correctly. Explicit routing away from list_3d_characters and list_presenters would make it more complete within this large sibling set.

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?

There are no input parameters, so the description has no parameter-documentation burden. Its saved-character scope is consistent with a parameterless listing and requires no additional invocation details.

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 opening clause gives a specific verb, resource, and scope: listing the user's saved characters. It also states that results include descriptions and style presets, but does not explicitly distinguish this tool from list_3d_characters or list_presenters.

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?

The second sentence provides three concrete triggers: a character is mentioned by name, the user asks who is saved, or a video will star someone. This is strong when-to-use guidance, though it gives no exclusions or sibling alternatives for 3D characters or presenters.

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

All Digital Maker AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?