Skip to main content
Glama

Mini XUI Proxy Trials

get_service_info

Read-only

Discover available VLESS Reality and Hysteria 2 proxy trial inbounds, quota, duration and available capacity. Free; no authentication.

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": "get_service_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description adds two genuinely useful behavioral facts: the call is free and requires no authentication. That is exactly the kind of context annotations cannot convey. The remaining gap is that idempotentHint=false hints at changing values, yet the description does not say whether availability/quota data is live or cached.

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?

Two short sentences: the resource enumeration comes first and the cost/auth qualifier second. No filler, no restatement of the tool name, and every clause carries information.

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

Completeness4/5

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

With zero params, existing annotations, and an output schema to carry return-value detail, the description needs only to establish what the endpoint surfaces and the access conditions, which it does. Only the freshness/liveness of the advertised capacity is left unaddressed.

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 no parameters, so the baseline is 4. Nothing in the description is needed to explain inputs, and it correctly implies the full result set is returned unfiltered.

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 specific verb ("Discover") and resource (available VLESS Reality and Hysteria 2 proxy trial inbounds, quota, duration, capacity), which is concrete enough to separate it from siblings like get_trial_status or create_trial. It falls short of naming how it differs from those siblings explicitly, but the resource is unambiguous.

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?

Usage is only implied: an agent can infer this is the discovery/catalog step before connecting or creating a trial, but the description never says when to call it versus get_trial_status or get_trial_connection, nor does it state prerequisites or exclusions.

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.

Resources