Skip to main content
Glama

Check if a username is taken

check_username
Read-onlyIdempotent

Check whether a Minecraft (Java Edition) or Roblox username is available, using the platforms' official lookups. Returns available, taken (with a profile link) or invalid (with the reason). Pair it with generate_names to find a free name. Results are cached for a minute.

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": {
      "platform": "<platform>",
      "name": "<name>"
    },
    "name": "check_username"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesUsername to check.
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the bar is lower. The description still adds real value by disclosing the three outcome states (available, taken with a profile link, invalid with a reason), the use of official platform lookups, and a one-minute result cache that affects freshness.

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?

Three short sentences, each doing work: purpose first, return values second, workflow pairing and caching last. No padding or restated title language.

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?

For a two-parameter lookup with no output schema, the description covers everything an agent needs: what it checks, the possible outcomes including the profile link, and the caching caveat. Annotations supply the safety profile, so nothing material is missing.

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 only 50%: name is documented in the schema but platform's enum carries no description. The description partially compensates by clarifying that Minecraft means Java Edition specifically, which is a meaningful distinction, but it adds no per-parameter guidance beyond that.

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?

The description gives a specific verb and resource (check username availability) and scopes it to two named platforms via their official lookups. It is clearly distinguishable from the sibling generate_names, which produces candidates rather than validating them.

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?

It explicitly tells the agent to pair this with generate_names to find a free name, which gives clear usage context in the naming workflow. It stops short of stating exclusions, such as unsupported platforms or what to do when a name is invalid, so it falls short of a full when/when-not statement.

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