Skip to main content
Glama
Sign In
urai-router

urai-router

Official
by etside
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

urai_models

List a merged catalogue of models from all configured providers, including free OpenCode Zen options, so you can discover available and no-cost models by provider or limit.

Instructions

List the merged model catalogue from all configured providers, including free OpenCode Zen models.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "urai_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
refreshNo
providerNo
free_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that results are merged across configured providers and include free OpenCode Zen models, but it does not explain caching, whether refresh triggers network work, auth requirements, or return shape. That is too thin for a four-parameter catalogue tool with zero 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 front-loaded sentence with no filler. It states the core resource and scope efficiently, though its brevity contributes to gaps covered in other dimensions.

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

Completeness2/5

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

With four undocumented parameters, no annotations, and no output schema, the definition is not complete enough for an agent to invoke the tool correctly. It establishes what is listed but not how the filters/options change results or what the call returns.

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%, and the description does not explain limit, refresh, provider, or free_only. The phrases 'all configured providers' and 'including free' loosely gesture at provider/free filtering, but defaults, value formats, and the meaning of refresh and limit are absent.

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 opens with a specific verb ('List') and resource ('merged model catalogue'), and names scope ('all configured providers') plus an inclusion ('free OpenCode Zen models'). It does not differentiate itself from siblings such as urai_refresh or urai_chat, so a 4 rather than 5.

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?

There is no explicit when-to-use guidance, no exclusions, and no mention of when to prefer urai_refresh or other siblings. The use case is only implied by the list verb, so an agent gets no routing help.

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

Deploy Server

Other Tools