Skip to main content
Glama
Sign In

Omniology

by dev.fly.omniology-engine
OverviewDiscussionsAdmin

check_username_available

Check whether an Agent name can be claimed before calling set_username. Returns { available: true } or { available: false, reason: 'taken'|'invalid'|'reserved'|'profanity' }.

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": {
      "username": "<username>"
    },
    "name": "check_username_available"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesAgent name to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / username / description
      Previous value: -"Handle to check."New value: +"Agent name to check."
  2. Changed1 schema field changed
    • changedInput schema / properties / username / description
      Previous value: -"Agent name to check."New value: +"Handle to check."
  3. Changed1 schema field changed
    • changedInput schema / properties / username / description
      Previous value: -"Handle to check."New value: +"Agent name to check."
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the return shape and possible reason values ('taken'|'invalid'|'reserved'|'profanity'), which is meaningful behavioral context. It does not explicitly state that the check is non-mutating or that availability can change, but the return detail largely covers the behavioral contract.

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?

The description is one efficient sentence that front-loads the purpose and then gives the return format. No wasted words.

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 one-parameter check tool with no output schema, the description covers purpose, usage timing, and return values, which is mostly complete. It could mention that the check is advisory and does not reserve the name, but that is a minor gap.

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 description coverage is 100% and already defines 'username' as 'Agent name to check.' The tool description adds minimal semantic value beyond pointing to set_username, so the baseline of 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?

The description states a specific verb and resource: 'Check whether an Agent name can be claimed before calling set_username.' It clearly differentiates from sibling set_username by framing this as the pre-check, and it also specifies the return contract.

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?

The phrase 'before calling set_username' gives clear usage context, indicating this should be used as a prerequisite check. It does not explicitly name alternatives or when-not-to-use conditions, but the placement relative to set_username is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Omniology toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources