Skip to main content
Glama

venice_list_models

List available Venice AI models by type to identify suitable options for text generation, image creation, speech synthesis, embeddings, and other AI tasks.

Instructions

List available Venice AI models by type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by model type (text, image, embedding, tts, asr, upscale, inpaint, video, or all)all

Implementation Reference

  • The main handler function for the 'venice_list_models' tool. It calls the Venice API with the provided type filter, parses the ModelsResponse, formats a list of models, and returns it as text content.
    async ({ type }) => {
      // Always pass type parameter - API may return only text models without it
      const endpoint = `/models?type=${type}`;
      const response = await veniceAPI(endpoint);
      const data = await response.json() as ModelsResponse;
      if (!response.ok) return { content: [{ type: "text" as const, text: `Error: ${data.error?.message || response.statusText}` }] };
      const models = data.data || [];
      const list = models.map((m) => `- ${m.id} (${m.type || m.object || "unknown"})`).join("\n");
      return { content: [{ type: "text" as const, text: `Available models (${models.length}):\n${list}` }] };
    }
  • Zod input schema for the tool, defining an optional 'type' parameter to filter models.
    { type: z.enum(["text", "image", "embedding", "tts", "asr", "upscale", "inpaint", "video", "all"]).optional().default("all").describe("Filter by model type (text, image, embedding, tts, asr, upscale, inpaint, video, or all)") },
  • Registration of the 'venice_list_models' tool on the MCP server, specifying name, description, input schema, and handler function.
    server.tool(
      "venice_list_models",
      "List available Venice AI models by type",
      { type: z.enum(["text", "image", "embedding", "tts", "asr", "upscale", "inpaint", "video", "all"]).optional().default("all").describe("Filter by model type (text, image, embedding, tts, asr, upscale, inpaint, video, or all)") },
      async ({ type }) => {
        // Always pass type parameter - API may return only text models without it
        const endpoint = `/models?type=${type}`;
        const response = await veniceAPI(endpoint);
        const data = await response.json() as ModelsResponse;
        if (!response.ok) return { content: [{ type: "text" as const, text: `Error: ${data.error?.message || response.statusText}` }] };
        const models = data.data || [];
        const list = models.map((m) => `- ${m.id} (${m.type || m.object || "unknown"})`).join("\n");
        return { content: [{ type: "text" as const, text: `Available models (${models.length}):\n${list}` }] };
      }
    );
  • Helper function 'veniceAPI' used by the tool handler to perform authenticated HTTP requests to the Venice AI API.
    export async function veniceAPI(endpoint: string, options: RequestInit = {}): Promise<Response> {
      const url = `${BASE_URL}${endpoint}`;
      const headers: Record<string, string> = {
        "Authorization": `Bearer ${API_KEY}`,
        "Content-Type": "application/json",
        ...(options.headers as Record<string, string> || {}),
      };
      return fetch(url, { ...options, headers });
    }
  • TypeScript interface 'ModelsResponse' used to type the API response data in the handler.
    export interface ModelsResponse extends VeniceAPIError {
      data?: Model[];
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool lists models but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, rate limits, pagination, or what the output format looks like. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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, efficient sentence that directly states the tool's purpose without any fluff. It's appropriately sized for a simple listing tool and front-loads the essential information.

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 no annotations, no output schema, and a simple parameter with full schema coverage, the description is incomplete. It doesn't explain what the output contains (e.g., model names, IDs, capabilities), authentication requirements, or error handling. For a tool that likely returns structured data, more context is needed to use it effectively.

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?

Schema description coverage is 100%, so the schema fully documents the single parameter 'type' with its enum values and default. The description adds minimal value beyond the schema by mentioning 'by type' but doesn't provide additional context about what the types mean or why to filter. Baseline 3 is appropriate when schema does the heavy lifting.

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 resource 'Venice AI models', specifying the action and target. It distinguishes from siblings by focusing on model listing rather than operations like chat, image generation, or API key management. However, it doesn't explicitly differentiate from 'venice_list_characters' which might be a related listing function.

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?

The description implies usage when needing to see available models by type, but provides no explicit guidance on when to use this versus alternatives like 'venice_list_characters' or when not to use it. It mentions filtering by type but doesn't explain why one would choose this tool over directly using a specific model tool.

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