Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Character Chat

venice_chat_with_character

Send chat messages to a Venice character by slug to hold character-based conversations, including uncensored prompts where the selected model permits.

Instructions

Chat with a Venice character by slug. Completion id and actual model, when returned upstream, are available in structured content. Responses marked X-Venice-TEE: true also include a JSON text block for venice_tee_signature. Note: the character lookup itself is API-key-only, but the chat completion supports x402 — so x402 users may need to fetch character info via API key first. Uncensored: NSFW prompts allowed where the model permits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "character_slug": "<character_slug>",
      "messages": "<messages>"
    },
    "name": "venice_chat_with_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo
messagesYes
max_tokensNo
temperatureNo
character_slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses three non-obvious traits: completion id and actual model surface in structured content, TEE-marked responses carry an extra JSON block for venice_tee_signature, and the auth asymmetry where character lookup is API-key-only while completion supports x402. The NSFW policy statement adds a further content-boundary caveat that annotations cannot express. Nothing here contradicts readOnlyHint=false or openWorldHint=true.

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 leads, then the response-shape note, then the auth caveat, then the content policy — a sensible order with no filler sentences. The middle sentences are dense and slightly run-on, packing structured content, TEE blocks, and x402 into two compressed clauses.

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?

The description compensates well for the missing output schema by explaining what structured content and the TEE text block contain. However, for a five-parameter chat tool with zero schema descriptions and no output schema, the input side remains thin — no guidance on messages shape, token limits, or model override — leaving real gaps for an agent composing a call.

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 0% across all five parameters, so the description must carry the burden and it largely does not. It only gestures at character_slug ('by slug'); model, messages, max_tokens, and temperature get no meaning at all — notably it never says whether the model parameter overrides the character's default model, which is exactly the ambiguity the structured-content note raises.

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 first sentence gives a specific verb and resource ('Chat with a Venice character by slug'), which clearly separates it from the generic venice_chat and from lookup tools like venice_get_character. It stops short of naming the sibling it replaces, so the differentiation is inferred from the resource rather than stated.

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 context is present but indirect: the x402 note explains that users paying via x402 must fetch character info with an API key first, and the 'Uncensored' line signals the content policy. There is no explicit statement of when to pick this over venice_chat or venice_responses, so the routing is implied rather than prescribed.

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