Skip to main content
Glama

venice_list_characters

Retrieve available AI character personas for roleplay interactions from Venice AI's collection.

Instructions

List available Venice AI character personas for roleplay

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of characters to return (default: 20)

Implementation Reference

  • The async handler function that fetches characters from the Venice API endpoint '/characters', processes the response by slicing to the requested limit, truncates descriptions to 100 chars, formats a markdown list, and returns it as text content.
    async ({ limit }) => {
      const response = await veniceAPI("/characters");
      const data = await response.json() as CharactersResponse;
      if (!response.ok) return { content: [{ type: "text" as const, text: `Error: ${data.error?.message || response.statusText}` }] };
      const chars = (data.data || []).slice(0, limit);
      const list = chars.map((c) => {
        const desc = c.description ? c.description.substring(0, 100) + (c.description.length > 100 ? "..." : "") : "";
        return `- ${c.name} (${c.slug}): ${desc}`;
      }).join("\n");
      return { content: [{ type: "text" as const, text: `Available characters (showing ${chars.length}):\n${list}\n\nNote: Use the slug to interact with a specific character.` }] };
    }
  • Zod schema defining the optional 'limit' parameter for the number of characters to list.
    { 
      limit: z.number().optional().default(20).describe("Maximum number of characters to return (default: 20)")
    },
  • Registers the 'venice_list_characters' tool on the MCP server using server.tool(), providing name, description, input schema, and inline handler implementation.
    server.tool(
      "venice_list_characters",
      "List available Venice AI character personas for roleplay",
      { 
        limit: z.number().optional().default(20).describe("Maximum number of characters to return (default: 20)")
      },
      async ({ limit }) => {
        const response = await veniceAPI("/characters");
        const data = await response.json() as CharactersResponse;
        if (!response.ok) return { content: [{ type: "text" as const, text: `Error: ${data.error?.message || response.statusText}` }] };
        const chars = (data.data || []).slice(0, limit);
        const list = chars.map((c) => {
          const desc = c.description ? c.description.substring(0, 100) + (c.description.length > 100 ? "..." : "") : "";
          return `- ${c.name} (${c.slug}): ${desc}`;
        }).join("\n");
        return { content: [{ type: "text" as const, text: `Available characters (showing ${chars.length}):\n${list}\n\nNote: Use the slug to interact with a specific character.` }] };
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action is to 'List' characters, implying a read-only operation, but doesn't cover critical aspects like authentication requirements, rate limits, pagination behavior, or error handling. This leaves significant gaps for a tool that likely interacts with an external API.

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?

The description is a single, clear sentence that efficiently conveys the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the returned character data includes (e.g., names, IDs, descriptions), how results are structured, or any behavioral traits like rate limits. For a tool that likely returns a list of personas, more context on the output is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'limit' parameter fully documented in the schema itself. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating value.

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 clearly states the verb 'List' and the resource 'Venice AI character personas for roleplay', making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'venice_list_models' or 'venice_list_api_keys' beyond specifying 'characters' versus 'models' or 'api_keys'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing authentication or API keys, or specify scenarios where listing characters is appropriate compared to other list operations like 'venice_list_models'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/georgeglarson/venice-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server