Skip to main content
Glama

Resolve a model name or suggest matches

playground_model_resolve
Read-onlyIdempotent

Read-only. Resolve user shorthand such as Seedream 5.0, Nano Banana 2 or Seedance 2 Mini against enabled models. Case, punctuation and trailing .0 are normalized. Unique matches return canonical IDs; ambiguous names and typos return suggestions for clarification. Never silently substitute a different version or default. No credits spent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "query": "<query>",
      "kind": "<kind>"
    },
    "name": "playground_model_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesModel family to resolve: image, video or audio.
queryYesModel name, shorthand or spelling supplied by the user to resolve to a canonical model ID.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
kindYes
nextNoSuggested next action; it does not authorize spending.
matchNo
modelNo
queryYes
statusYes
suggestionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds substantive behavior: normalization of case, punctuation and trailing .0, distinct outcomes for unique vs ambiguous matches, a hard guarantee of no silent version substitution, and the fact that no credits are spent. These are exactly the traits an agent needs before trusting the returned ID.

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?

Five short sentences, front-loaded with 'Read-only.' and the core action, followed by normalization, outcome, and safety guarantees in descending order of importance. No filler or repetition of the title beyond what is needed.

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?

An output schema exists, so return shape need not be explained; the description covers the remaining unknowns an agent faces: normalization behavior, ambiguity handling, and the no-substitution/no-cost guarantees. Nothing material is missing for a three-parameter read-only resolver.

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 all three parameters (query, kind, projectId) are already documented in the schema. The description adds only indirect context via 'user shorthand' and 'enabled models' (implying project-scoped resolution) but gives no format or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Resolve user shorthand ... against enabled models') and grounds it with three concrete examples (Seedream 5.0, Nano Banana 2, Seedance 2 Mini). The function is unmistakably a name-to-ID resolver, which no sibling in the list performs, so an agent can select it without ambiguity.

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 context of use is clear: it takes a user-supplied name and either returns a canonical ID or suggestions for clarification. It does not explicitly name an alternative tool or state when NOT to call it (e.g. 'call this before media_generate rather than guessing an ID'), so there are no explicit exclusions or routing rules.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.