Skip to main content
Glama

List AI influencers

kreavo_list_characters
Read-onlyIdempotent

List your AI influencer characters

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": "kreavo_list_characters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that: no mention of scope (the calling user's characters only), pagination or result limits, or what an empty result means. It does not contradict the annotations, but it contributes no behavioral context of its own.

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?

A single short sentence with no filler and the key information up front. It is not verbose, though its brevity reflects under-specification rather than disciplined editing, which is captured in the other dimensions.

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?

For a zero-parameter read tool this is close to the minimum viable amount of text, and the annotations carry the safety story. However, there is no output schema, so the description is the only place an agent could learn what a character record contains or that the returned character identifiers feed into kreavo_generate_image / kreavo_generate_photoshoot, and that information is absent.

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?

The tool takes zero parameters and the schema is empty, so there is no parameter semantics to explain; baseline 4 applies. The description correctly does not invent parameters that do not exist.

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

Purpose3/5

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

The description supplies a verb ("List") and a resource ("AI influencer characters"), so the basic operation is inferable. But it is essentially a restatement of the title "List AI influencers" with a possessive added, and it does nothing to distinguish this from siblings like kreavo_list_scenes or kreavo_list_models, which are also list operations in the same namespace.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus kreavo_list_scenes, kreavo_list_models, or kreavo_create_character. No prerequisites, no mention of whether characters must exist first, and no indication of whether this is a prerequisite step before generation tools that reference a character.

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