Skip to main content
Glama
Sign In
urai-router

urai-router

Official
by etside
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

urai_ensure_proxy

Start the local OpenAI-compatible proxy in the background when it is not running, then return its base URL for immediate client use.

Instructions

Start the local OpenAI-compatible proxy in the background if needed and return its base URL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses that the proxy starts in the background and returns a base URL, but omits important details such as whether the operation is idempotent, what happens on port conflicts, error behavior, lifecycle management, or whether authentication is required.

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 wasted words. It efficiently conveys the action, background behavior, conditional nature, and return value.

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 ensure-style tool, the description covers the core action and return value. However, without annotations or an output schema, it leaves gaps around idempotency guarantees, failure modes, and how the returned base URL should be used by sibling tools.

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, so there is no parameter semantics to explain. Per the baseline for parameterless tools, this dimension defaults to 4.

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 states a specific verb and resource: start the local OpenAI-compatible proxy in the background. It is clear what the tool does, though it does not explicitly differentiate itself from siblings like urai_setup or urai_check.

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 phrase 'if needed' implies idempotent ensure-style usage, suggesting the agent can call it without first checking whether the proxy is running. However, there is no explicit guidance on when to prefer this over urai_setup or urai_check, and no exclusions or prerequisites are stated.

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