Skip to main content
Glama

Your characters

list_characters
Read-onlyIdempotent

Your characters and products, newest first: id, name, kind ("person" for a character, "object" for a product, also given as kindLabel), the brands it belongs to (brandIds, see list_brands), whether the identity sheet that keeps the face consistent is ready, whether they have a voice, which social platforms are connected for posting, and a link to the profile image that expires in an hour.

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
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds context annotations cannot: default ordering (newest first), the one-hour expiry on the profile image link, and the meaning of kind/kindLabel and the readiness flags — all real behavioral detail.

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?

Purpose is front-loaded in the first clause, then the field list follows in a single packed sentence. It is long but each clause maps to a distinct returned attribute; minor density cost comes from parenthetical asides like the kindLabel and list_brands references.

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?

With no output schema, describing the return shape is the right use of the description, and it does that thoroughly, including the expiring image link. The only real gap is the undocumented limit parameter and the absence of any statement that results are capped or how to page through more than the limit.

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?

There is one parameter (limit, default 20, max 50) and schema description coverage is 0%, so the description was the only place to explain it — yet it is never mentioned. The field enumeration describes outputs, not the input, so parameter meaning is entirely unaddressed.

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?

Opens with a specific verb+resource ("Your characters and products, newest first") and enumerates the returned fields, so an agent knows exactly what this lists. It references list_brands for brand lookups, giving partial differentiation, but never distinguishes itself from get_character, which could plausibly serve overlapping needs.

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 implied by the field list — it's the enumeration endpoint for characters and products — and the pointer to list_brands shows where brand detail lives. There is no explicit statement of when to prefer this over get_character for a single item, nor any prerequisite or exclusion guidance.

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