Replicate

Model Version

model_version

Read-onlyIdempotent

Fetch full metadata for a specific Replicate model version by owner, name, and version_id, including the complete input/output OpenAPI schema and Cog version.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "stable-diffusion",
      "owner": "stability-ai",
      "version_id": "f178fa7a1ae43a9d672b0d1c6c1c0c5e1234abcd"
    },
    "name": "model_version"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`owner`	Yes
`version_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 11, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds return-content context ('complete input/output OpenAPI schema and Cog version'), which is useful but limited beyond the structured annotations.

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 well-formed sentence that front-loads the action and resource, then adds the return-content detail. Every clause earns its place with no redundancy.

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?

Given three required parameters, no output schema, and rich annotations, the description is adequate but has clear gaps. It explains what is returned but omits routing guidance against similar sibling tools and adds no parameter semantics.

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%, so the description must compensate. It merely repeats the three parameter names (owner, name, version_id) without adding format, expected values, or meaning beyond what the schema's examples provide.

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 ('Fetch') and resource ('metadata for a specific Replicate model version') with identifying parameters. It does not explicitly distinguish itself from close siblings like 'model' or 'model_versions', so it falls short of the 5 benchmark.

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?

No guidance is given on when to use this tool versus alternatives such as 'model' or 'model_versions'. The description only implies usage through the required parameters, with no explicit when-to-use or exclusions.

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

All Replicate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.