Skip to main content
Glama

Mini XUI Proxy Trials

create_trial

Reserve a free 1 GiB, 30-minute proxy trial using an inbound from get_service_info. Returns an ID and secret access_token. This has side effects, consumes a slot, and is not idempotent. If ready is false, poll get_trial_status. Never publish or log the token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inbound": "<inbound>"
    },
    "name": "create_trial"
  }
}

Input Schema

NameRequiredDescriptionDefault
inboundYesAn inbound identifier from get_service_info, such as in-1443-hysteria or in-443-tcp.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag readOnly=false and idempotent=false, but the description adds information they do not carry: that a scarce slot is consumed, that readiness is asynchronous and requires polling get_trial_status, and that the returned token is a secret that must never be published or logged. This is exactly the behavioral context an agent needs before invoking a mutating, quota-consuming call.

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?

Four short sentences, front-loaded with the resource and its quota, then returns, then side effects, then the polling branch and the security constraint. Every sentence carries distinct, actionable information with no padding.

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

Completeness5/5

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

An output schema exists, so the description needn't enumerate return fields, and it still notes the ID and access_token. Combined with the polling guidance, quota warning, and token-handling rule, an agent has everything needed to call this correctly and follow up afterward.

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

Parameters3/5

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

With a single parameter at 100% schema description coverage, the schema already explains that the inbound identifier comes from get_service_info and gives examples. The description's mention of the inbound source is redundant with the schema, so it adds no meaning beyond the structured field; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus concrete scope: reserve a free 1 GiB, 30-minute proxy trial from an inbound. It also names where the input comes from (get_service_info) and what comes back (ID and secret access_token), which separates it from the status and connection siblings.

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

Usage Guidelines5/5

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

Gives the prerequisite (inbound from get_service_info), the follow-up path (if ready is false, poll get_trial_status), and an implicit warning against repeat calls via 'consumes a slot, and is not idempotent.' That routes the agent to the correct sibling without leaving anything to inference.

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