Skip to main content
Glama
Sign In
urai-router

urai-router

Official
by etside
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

urai_stats

Displays routing statistics, key health, and catalogue details to help you inspect LLM API key status and routing behavior.

Instructions

Show routing statistics (same as health plus catalogue details).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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. "Show" reasonably signals a non-mutating read, and the health-superset framing hints at volume/scope, but it does not state read-only semantics explicitly, nor permissions, cost, or payload characteristics.

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?

A single front-loaded sentence with a clarifying parenthetical and no padding. Slight ambiguity comes from relying on the reader already knowing what urai_health returns, but nothing is wasted.

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?

For a zero-parameter diagnostic tool with no annotations and no output schema, the description should at least characterize the returned data. "Catalogue details" is left undefined, so an agent cannot anticipate whether the payload includes models, keys, or proxy configuration.

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

Parameters4/5

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

The tool takes zero parameters and the schema description coverage is 100%, so there is no parameter meaning to add. The description does contribute a hint about what the response contains (routing stats plus catalogue details), which is the only useful semantic content available here.

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?

States a concrete verb and resource ("Show routing statistics") and positions it relative to a sibling by saying it is "same as health plus catalogue details," which lets an agent distinguish it from urai_health. However, "routing statistics" and "catalogue details" remain underspecified in domain terms.

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

Usage Guidelines3/5

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

The parenthetical implies a selection rule (this is a superset of urai_health), so an agent can infer when to prefer it, but the guidance is only implied. There is no explicit when-to-use, when-not-to-use, or named alternative beyond the passing reference to health.

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