Skip to main content
Glama

Mini XUI Proxy Trials

get_trial_connection

Read-only

Return a secret VLESS or Hysteria 2 connection link for an active trial. Requires its ID and access_token. Never publish or log the returned link.

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": {
      "id": "<id>",
      "access_token": "<access_token>"
    },
    "name": "get_trial_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTrial account ID returned by create_trial.
access_tokenYesSecret token returned by create_trial; disclose only to trusted clients.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description adds a real operational constraint: the returned value is secret material that must never be published or logged. It does not explain the consequence of idempotentHint=false (e.g., whether each call mints a fresh link and invalidates the prior one), which is the main behavioral gap.

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, front-loaded with the action and output type, followed by the security constraint. Nothing is redundant or padded.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers the key sensitivity handling and prerequisites. It could be more complete by noting behavior for expired/inactive trials or whether repeated calls rotate the link.

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?

Schema coverage is 100%, and the schema already explains that id comes from create_trial and access_token is a secret token. The description only restates that both are required, adding no syntax, format, or provenance detail beyond the schema.

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 gives a specific verb and resource ('Return a secret VLESS or Hysteria 2 connection link') scoped to 'an active trial', which is far more informative than the bare name. It does not explicitly contrast itself with get_trial_status, but the output type (a connection link) is distinctive enough that an agent can tell them apart.

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 'for an active trial' implies a precondition, and the two required inputs are named, but there is no explicit statement of when to call this instead of get_trial_status or what to do if the trial is not active. Usage is inferable rather than guided.

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