Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice List Characters

venice_list_characters
Read-onlyIdempotent

Retrieve, filter, and sort public Venice characters by tags, search, ratings, and models to find characters for chats; an API key is required.

Instructions

List public Venice characters. API key required — this endpoint does not accept x402 wallet auth.

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

Input Schema

NameRequiredDescriptionDefault
tagNoDeprecated: use tags. A single tag, merged into tags.
tagsNo
isProNo
limitNo
offsetNo
searchNo
sortByNo
isAdultNo
modelIdNo
sortOrderNo
categoriesNo
isWebEnabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.3.0
    • addedInput schema / properties / categories
      Added value: +{
      +  "items": {
      +    "maxLength": 100,
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / isAdult
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / isPro
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / isWebEnabled
      Added value: +{
      +  "type": "boolean"
      +}
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +100
    • addedInput schema / properties / modelId
      Added value: +{
      +  "items": {
      +    "maxLength": 200,
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / search / maxLength
      Added value: +200
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "enum": [
      +    "featured",
      +    "highestRating",
      +    "highlyRated",
      +    "highlyRatedAndRecent",
      +    "imports",
      +    "mostRecent",
      +    "ratingCount"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "enum": [
      +    "asc",
      +    "desc"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / tag / description
      Added value: +"Deprecated: use tags. A single tag, merged into tags."
    • addedInput schema / properties / tag / maxLength
      Added value: +100
    • addedInput schema / properties / tags
      Added value: +{
      +  "items": {
      +    "maxLength": 100,
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
  2. First observedv0.2.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds non-redundant behavioral context by disclosing the authentication constraint and the x402 exclusion, which the agent cannot infer from the schema. It omits pagination/sorting defaults and any indication of result size, keeping it short of a 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?

Two sentences, both front-loaded and free of filler; the resource is identified first and the auth caveat second. Nothing is wasted, though the extreme brevity is partly the source of the parameter gap.

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?

For a tool with 12 optional parameters, near-zero schema descriptions, and no output schema, the description is far too thin. It never explains filtering, pagination behavior, default sort, or what a returned character record looks like, leaving the agent under-equipped to call it correctly.

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?

Schema description coverage is only 8% across 12 parameters – only the deprecated 'tag' field carries any documentation. The description explains none of the meaningful filters (tags, categories, isPro, isAdult, search, sortBy, sortOrder, limit/offset, modelId), so an agent must guess at semantics and interactions from names and enums alone.

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 states a specific verb and resource ('List public Venice characters'), which clearly separates it from siblings like venice_get_character and venice_chat_with_character. It does not explicitly name those siblings, but the 'list public' framing is unambiguous.

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?

It supplies a real usage prerequisite ('API key required — this endpoint does not accept x402 wallet auth'), which tells the agent which credential path to take. However, it gives no guidance on when to pick this over venice_get_character, venice_character_reviews, or venice_chat_with_character, so the when-to-use logic is only implied by the tool name.

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