Skip to main content
Glama

Inspect Ubi account and availability

get_account
Read-onlyIdempotent

Inspect sign-in status, available features and quota reset dates. require_login=true requests OAuth for an explicit sign-in request. Guests can browse public models. Sign in for research data, projects and server runs.

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

Input Schema

NameRequiredDescriptionDefault
require_loginNo

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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds something the annotations cannot: that require_login=true initiates an OAuth flow, an interactive side effect an agent must not trigger casually, plus which capabilities are gated behind login. Return-shape detail is absent, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short, front-loaded statements with no filler; the core purpose comes first and the parameter behavior second. The phrasing is slightly telegraphic ('requests OAuth for an explicit sign-in request'), which costs a bit of clarity but nothing is wasted.

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 one optional parameter, rich annotations, and an output schema covering return values, the description supplies everything needed to decide whether and how to call it. Only the true/false behavioral difference in the response is left implicit, a small omission for a tool this simple.

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?

Schema description coverage is 0%, so the description must carry the lone parameter, and it does: require_login=true is explicitly tied to requesting OAuth for a deliberate sign-in. It doesn't state what gets returned when require_login is false versus true, leaving a minor gap.

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 object set: inspect sign-in status, available features, and quota reset dates. This is clearly an account/auth-state tool, distinct from the resource getters (get_model, get_project) in the sibling list. It stops short of naming a sibling it could be confused with, so it lands at 4 rather than 5.

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 concrete conditions: guests can browse public models, while research data, projects, and server runs require sign-in, and require_login=true is only for an explicit sign-in request. That is real when-to-use and when-not-to-use guidance, though it frames the choice as guest vs. signed-in rather than pointing at specific alternative tools.

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