Skip to main content
Glama
veniceai

Venice MCP Server

Official
by veniceai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Venice List Characters

venice_list_characters
Read-onlyIdempotent

List public Venice characters with search, tag, category, model, rating, and adult filters. API key required; x402 wallet auth is not accepted.

Instructions

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

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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and non-open-world, so the safety profile is covered. The description adds the useful auth-method constraint, but says nothing about size of result sets, pagination, or filtering behavior for a 12-parameter query tool.

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 tight sentences with the purpose front-loaded and zero filler; the auth constraint follows immediately. It is efficient, though the extreme brevity also reflects the missing filter coverage.

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 12-filter listing tool with no output schema and near-zero schema coverage, the description is far too thin: no return shape, no pagination semantics, no filter documentation. Only the auth requirement is covered.

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

Parameters1/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, and the description compensates for none of them — no mention of tags, categories, sorting, pagination, or the deprecated tag field. With this much undocumented surface, the description carries no parameter meaning at all.

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 gives a specific verb+resource ('List public Venice characters'), which clearly separates it from the singular sibling venice_get_character. It does not explicitly name sibling alternatives, so it stops just short of a 5.

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 adds a real routing constraint — API key required, x402 wallet auth not accepted — which tells the agent how to authenticate. However, it gives no guidance on when to use this vs. venice_get_character, venice_character_reviews, or the other list endpoints, and no exclusion conditions.

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

Deploy Server

Other Tools