Skip to main content
Glama
Cicatriiz

Civitai MCP Server

get_model_version

Retrieve detailed information about a specific AI model version by providing its unique ID, enabling users to access and manage model data on the Civitai MCP Server.

Instructions

Get detailed information about a specific model version

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelVersionIdYesThe ID of the model version to retrieve

Implementation Reference

  • Executes the tool logic: fetches model version via client and formats response as formatted text content.
    private async getModelVersion(args: any) {
      const { modelVersionId } = args;
      const version = await this.client.getModelVersion(modelVersionId);
      
      return {
        content: [
          {
            type: 'text',
            text: `# ${version.model.name} - ${version.name}\\n\\n` +
              `**Model Type:** ${version.model.type}\\n` +
              `**Version ID:** ${version.id}\\n` +
              `**Created:** ${new Date(version.createdAt).toLocaleDateString()}\\n` +
              `**Downloads:** ${version.stats.downloadCount?.toLocaleString() || 0}\\n` +
              `**Rating:** ${version.stats.rating?.toFixed(1) || 'N/A'}\\n\\n` +
              `**Trained Words:** ${version.trainedWords.join(', ') || 'None'}\\n\\n` +
              `**Description:**\\n${version.description}\\n\\n` +
              `**Files (${version.files?.length || 0}):**\\n${version.files?.map(file => 
                `- Size: ${file.sizeKb ? (file.sizeKb / 1024).toFixed(1) : 'Unknown'} MB\\n` +
                `  Format: ${file.metadata?.format || 'Unknown'}\\n` +
                `  FP: ${file.metadata?.fp || 'Unknown'}\\n` +
                `  Scans: Pickle=${file.pickleScanResult || 'Unknown'}, Virus=${file.virusScanResult || 'Unknown'}\\n`
              ).join('\\n') || 'No files available'}\\n` +
              `**Sample Images:** ${version.images.length} available`,
          },
        ],
      };
    }
  • src/index.ts:142-152 (registration)
    Tool registration in the getTools() method, defining name, description, and input schema.
    {
      name: 'get_model_version',
      description: 'Get detailed information about a specific model version',
      inputSchema: {
        type: 'object',
        properties: {
          modelVersionId: { type: 'number', description: 'The ID of the model version to retrieve' },
        },
        required: ['modelVersionId'],
      },
    },
  • Input schema defining the required modelVersionId parameter.
    inputSchema: {
      type: 'object',
      properties: {
        modelVersionId: { type: 'number', description: 'The ID of the model version to retrieve' },
      },
      required: ['modelVersionId'],
    },
  • Dispatch handler in the CallToolRequestSchema switch statement.
    case 'get_model_version':
      return await this.getModelVersion(args);
  • CivitaiClient helper method that makes the API request to fetch model version data.
    async getModelVersion(modelVersionId: number): Promise<ModelVersionResponse> {
      const url = this.buildUrl(`/model-versions/${modelVersionId}`);
      return this.makeRequest<ModelVersionResponse>(url, ModelVersionResponseSchema);
    }
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. While 'Get detailed information' implies a read-only operation, it doesn't specify what 'detailed information' includes, whether authentication is required, rate limits, error conditions, or the format of the returned data. This leaves significant gaps in understanding the tool's behavior.

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 unnecessary words. It's 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 for a tool that retrieves 'detailed information'. It doesn't specify what information is returned, potential errors, or usage context, leaving the agent with insufficient guidance to effectively use the tool beyond the basic parameter requirement.

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 schema description coverage is 100%, with the single parameter 'modelVersionId' clearly documented in the schema. The description adds no additional meaning beyond what the schema provides, such as examples of valid IDs or context about where to find them. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 action ('Get detailed information') and the target ('about a specific model version'), which is a specific verb+resource combination. However, it doesn't distinguish this tool from similar siblings like 'get_model' or 'get_model_version_by_hash', which likely retrieve related information about models or model versions.

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. With multiple sibling tools like 'get_model', 'get_latest_models', and 'get_model_version_by_hash', there's no indication of when this specific tool is appropriate or what differentiates it from others in the context.

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

Related 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/Cicatriiz/civitai-mcp-server'

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