Skip to main content
Glama
K1ta141k

mcp-bench-router

by K1ta141k

query_design_model

Send a design prompt to the top-ranked model from designarena.ai's leaderboard via OpenRouter, with category-specific model selection for website, game, 3D, image, video, and more.

Instructions

Send a design prompt to the best available model on OpenRouter, automatically selected from designarena.ai rankings. Skips models not available on OpenRouter. Requires OPENROUTER_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesThe design prompt to send to the best available model.
categoryNoDesign category to select the best model from. Options: allcategories, website (models generate a complete website from a text prompt), gamedev (models generate a playable browser game from a text prompt), 3d (models generate an interactive 3d scene from a text prompt), dataviz (models generate interactive data visualizations from a text prompt), uicomponent (models generate a production-ready ui component from a text prompt), image (models generate an image from a text prompt), logo (models generate a logo design from a text prompt), svg (models generate svg markup from a text prompt), video (models generate a video from a text prompt), imagetoimage (models transform an existing image based on a text prompt), slides (models generate a presentation from a text prompt), graphicdesign (models generate graphic design assets (posters, banners, marketing materials) from a text prompt), tts (models generate speech audio from text input). Defaults to "allcategories".
max_tokensNoMaximum tokens in the response.
temperatureNoSampling temperature (0-2).
Behavior4/5

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

No annotations are provided, so description fully carries the burden. It discloses selection behavior (automatically selected, skips unavailable models) and the required API key. However, it does not mention error handling or what happens if no model is available.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is two sentences that efficiently convey the main action and requirement. It is front-loaded with the core purpose. However, it could be slightly more structured by separating the selection logic and requirement.

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?

No output schema exists, but description does not mention what the tool returns (e.g., raw response, model name, or error). It also lacks details on the selection algorithm beyond 'best available', leaving some ambiguity for an agent without additional context.

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 baseline is 3. The description does not add new meaning beyond the schema; it merely repeats the prompt and category concepts. No extra context on how parameters affect the selection or output.

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?

Description clearly states the verb 'send', the resource 'design prompt', and identifies the selection mechanism 'best available model on OpenRouter' from designarena.ai rankings. It distinguishes from sibling tools like query_specific_model by emphasizing automatic selection.

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?

Description explains when to use it (send design prompt to best model) and mentions a prerequisite (OPENROUTER_API_KEY). It implies not to use when targeting a specific model, but does not explicitly state alternatives despite sibling tool names.

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/K1ta141k/mcp-bench-router'

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