Skip to main content
Glama
Sign In
urai-router

urai-router

Official
by etside
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

urai_refresh

Reload keys.txt and refresh provider model catalogues to apply updated API keys and model lists. Set force to bypass cached catalogue data when needed.

Instructions

Reload keys.txt and refresh provider model catalogues.

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_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo

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?

With no annotations, the description carries the full behavioral burden, yet it does not say whether this mutates on-disk state, whether it is cheap or expensive, whether reloads are idempotent, or what happens to in-flight state. The word "refresh" implies a cache/catalogue invalidation side effect that is never described.

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?

One short sentence with the two effects front-loaded and no filler. It is efficient, though it is arguably too terse given the unexplained parameter and side effects.

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?

The tool is simple (one optional boolean, no output schema), so a short description is defensible. However, the undefined "force" flag and the undisclosed side effects mean an agent cannot confidently decide when to set it or what to expect afterward.

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 coverage is 0% and the description never mentions the single optional parameter "force", so the agent gets no meaning for it beyond the bare name. Whether force bypasses caching, forces a network re-fetch, or is required for changed keys remains unknown.

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?

"Reload keys.txt and refresh provider model catalogues" states specific verbs and resources, so an agent can tell this is a reload/refresh operation rather than a query. It implicitly distinguishes itself from urai_keys and urai_models but never names those siblings or explains how it differs from them.

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 guidance on when to call this versus urai_keys, urai_models, urai_setup, or urai_health, nor any mention of when a reload is needed (e.g., after editing keys.txt). No exclusions or prerequisites are given, leaving the agent to infer usage entirely.

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