Skip to main content
Glama

Recommend the Best Model for a Task

replicate_recommend_model
Read-onlyIdempotent

Rank curated AI models by speed, cost, quality, or balanced priority. Get top 5 recommendations with cost estimates and reasoning to pick the right model for your task.

Instructions

Rank the curated models in a category by a priority (speed, cost, quality, or balanced) and return recommendations with cost estimates and reasoning. This does NOT run anything — it advises which model to use.

Workflow: call this to pick a model, then call the matching generate tool (e.g. replicate_generate_image) with model set to the recommended key.

Args:

  • category (required): One of image, video, audio, tts, llm, vision, upscale, bg, stt, inpaint, segment, embed, voiceclone, threed, lipsync.

  • priority (default "balanced"): "speed" (fastest), "cost" (cheapest), "quality" (best), or "balanced" (weighted).

  • task_description (optional): Free text. Keyword hints like "quick draft" or "professional logo" nudge balanced ranking.

  • max_cost_usd (optional): Exclude models estimated above this cost.

  • duration_seconds (optional, 1–600): For per-second-priced categories (video, audio), used in cost estimation.

Returns structuredContent: { category, priority, recommendations: [{ key, model_id, speed, est_cost_usd, score, reason }], // top 5 count }

Examples:

  • category="image", priority="speed" → flux-schnell first

  • category="image", priority="quality" → highest-fidelity model first

  • category="video", priority="cost", duration_seconds=5 → cheapest per-5s clip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesWhich model category to recommend within.
priorityNoOptimization target. speed=fastest, cost=cheapest, quality=best, balanced=weighted blend. Default: balanced.balanced
max_cost_usdNoOptional cap — exclude models whose estimated cost exceeds this. Models with unknown pricing are always included regardless of this cap.
duration_secondsNoFor per-second-priced categories (video, audio), the expected duration used in cost estimation.
task_descriptionNoOptional task description. Keyword hints (e.g. 'quick draft' or 'professional logo') nudge balanced-mode ranking.
Behavior5/5

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

Annotations indicate readOnlyHint, idempotentHint, and destructiveHint are all appropriately set. The description adds: 'This does NOT run anything — it advises which model to use,' aligning with annotations and providing extra clarity. No contradictions.

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 concise and well-structured: intro, workflow, args, return format, examples. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description provides a structured return format example. It covers inputs, outputs, and workflow, making it complete for an advisory tool.

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

Parameters5/5

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

Schema coverage is 100%, and the description reiterates each parameter with additional context and examples. It explains the enum values, defaults, and optional behavior, adding significant value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool ranks curated models by priority and returns recommendations. It uses specific verbs (rank, recommend) and identifies the resource (models in a category). It distinguishes itself from sibling tools like replicate_generate_* by explicitly noting it does not run anything.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a workflow: call this to pick a model, then call a generate tool. This provides clear guidance on when to use it. However, it does not explicitly mention when not to use or contrast with alternatives like replicate_estimate_cost.

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

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