Skip to main content
Glama

Mini XUI Proxy Trials

get_trial_status

Read-only

Get a trial's expiry, approximate usage and active state. Requires the ID and secret access_token from create_trial. Keep both private.

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

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds meaningful behavior beyond that by flagging the credential requirement and the need to keep both values private, and by disclosing that usage figures are 'approximate.' It does not cover failure modes (expired/invalid token) or rate limits, so it is not exhaustive.

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: purpose first, credentials/privacy second. Every clause carries information an agent needs, with no filler or redundancy.

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?

For a two-parameter read tool with a full schema, complete annotations, and an output schema, the description covers purpose, prerequisites, and secrecy handling. What remains missing is error/permission behavior when credentials are invalid or expired, a modest gap given the otherwise rich structured fields.

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 says both values come from create_trial, including the 'disclose only to trusted clients' note. The description's mention of the ID and token largely restates the schema, adding no new syntax or format meaning, so baseline 3 applies.

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 and resource plus the exact fields returned: 'Get a trial's expiry, approximate usage and active state.' That is enough to separate it from create_trial, though the remaining sibling get_trial_connection is not addressed, so full sibling differentiation is not achieved.

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

Usage Guidelines4/5

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

Gives a clear prerequisite for use: it 'Requires the ID and secret access_token from create_trial,' which tells the agent this must follow create_trial. No explicit when-not-use or exclusion is stated, so it stops short of a 5.

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