Skip to main content
Glama
gerred

MCP Server Replicate

list_templates

Browse available AI model templates and their schemas for image generation using the Replicate API.

Instructions

List all available templates with their schemas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The list_templates tool handler function that iterates over the TEMPLATES dictionary and returns a structured dictionary with each template's schema, description, and version.
    def list_templates() -> dict[str, Any]:
        """List all available templates with their schemas."""
        return {
            name: {
                "schema": template["parameter_schema"],
                "description": template.get("description", ""),
                "version": template.get("version", "1.0.0"),
            }
            for name, template in TEMPLATES.items()
        }
  • The @mcp.tool() decorator registers the list_templates function as an MCP tool on the FastMCP server instance.
    def list_templates() -> dict[str, Any]:
        """List all available templates with their schemas."""
        return {
            name: {
                "schema": template["parameter_schema"],
                "description": template.get("description", ""),
                "version": template.get("version", "1.0.0"),
            }
            for name, template in TEMPLATES.items()
        }
  • Definition of the TEMPLATES dictionary used by list_templates, aggregating various preset configurations.
    TEMPLATES: dict[str, dict[str, Any]] = {
        "quality": QUALITY_PRESETS,
        "style": STYLE_PRESETS,
        "aspect_ratio": ASPECT_RATIO_PRESETS,
        "negative_prompt": NEGATIVE_PROMPT_PRESETS,
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without disclosing behavioral traits. It doesn't mention if this is a read-only operation, pagination behavior, rate limits, authentication needs, or what 'schemas' entail in the output, leaving significant gaps.

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 front-loads the core action ('List all available templates') without any wasted words. It's appropriately sized for a simple tool with no parameters.

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 the tool's simplicity (0 params, no output schema, no annotations), the description is minimally adequate but lacks depth. It doesn't explain what 'schemas' includes or behavioral context, making it incomplete for full agent understanding despite the low complexity.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add param info, which is fine here, but it could slightly clarify output semantics (e.g., what 'schemas' means), keeping it from a perfect score.

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 ('all available templates with their schemas'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_collections' or 'list_models' beyond mentioning templates specifically, which prevents a perfect score.

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 like 'validate_template_parameters' or other list tools. It lacks context about prerequisites, timing, or exclusions, offering only a basic statement of function.

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/gerred/mcp-server-replicate'

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