Skip to main content
Glama

OSIR Domain Registrar

by com.osir

checkKeywordAvailability

Read-onlyIdempotent

checkKeywordAvailability: Check keyword availability across all supported TLDs and registries with detailed per-domain results. Use checkKeywordAvailabilitySummary instead when you only need counts; it is faster.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tldsNoComma-separated TLDs without leading dots, e.g. "com,net".
keywordYesKeyword to check, without a TLD, e.g. "example".
registriesNoComma-separated registry filter, e.g. "verisign,pir,id,centralnic".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / keyword / description
      Added value: +"Keyword to check, without a TLD, e.g. \"example\"."
    • addedInput schema / properties / registries / description
      Added value: +"Comma-separated registry filter, e.g. \"verisign,pir,id,centralnic\"."
    • addedInput schema / properties / tlds / description
      Added value: +"Comma-separated TLDs without leading dots, e.g. \"com,net\"."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context beyond that: the operation spans all supported TLDs and registries and returns detailed per-domain results. It doesn't mention rate limits or result structure, but the additive scope and detail-level information earn it slightly above baseline.

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?

The description is compact and front-loaded, with the core purpose in the first sentence and a useful alternative in the second. It loses one point for the redundant 'checkKeywordAvailability:' prefix that merely repeats the tool name already known from the context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is sufficient for basic selection and invocation: it states scope, result granularity, and when to use the faster alternative. However, since there is no output schema, the phrase 'detailed per-domain results' is vague about what fields the agent should expect, and it doesn't clarify default behavior when tlds or registries are omitted beyond the implicit 'all supported.'

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%, so the schema fully documents keyword, tlds, and registries. The description adds no parameter-specific syntax or semantics beyond what the schema already provides, making the baseline of 3 appropriate.

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 begins with a specific verb and resource: 'Check keyword availability across all supported TLDs and registries with detailed per-domain results.' It also distinguishes this tool from the summary variant by emphasizing detailed per-domain results, so an agent can identify its unique purpose without opening sibling schemas.

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

Usage Guidelines5/5

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

The description explicitly names the alternative tool, checkKeywordAvailabilitySummary, and gives the condition for choosing it: 'when you only need counts; it is faster.' This is clear, actionable routing guidance that leaves little to inference.

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

All OSIR Domain Registrar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most tools target distinct resource-action pairs, but there are several overlapping clusters: six domain-suggestion tools (addPrefixToDomain, addSuffixToDomain, generateDomainSuggestions, bulkDomainSuggestions, spinDomainWords, suggestAlternatives) and overlapping account-info tools (getMyProfile, getAccountSummary, getRecentActivity, getMyAuditLogs). Descriptions help, but with 105 tools an agent will regularly face near-identical choices.

Naming Consistency4/5

The dominant convention is verbNoun camelCase (createContact, listDnsRecords, updateNameservers), which is readable and predictable. Deviations exist in the osirApp* and osirSite* families, where the noun precedes the verb, and a few names like suggestAlternatives and spinDomainWords break the pattern.

Tool Count1/5

105 tools is far beyond a coherent MCP server surface; even if the platform genuinely spans domains, DNS, email, VPS, billing, and app hosting, this should be split into focused servers. Many tools are single-purpose getters that add selection overhead rather than earning their place as one integrated set.

Completeness4/5

The covered services have broad CRUD/lifecycle coverage: contacts, DNS, hosts, domains, email, VPS, SSH keys, invoices, and Osir apps all have create/read/update/delete paths. Some registrar-specific operations (e.g., contact reassignment after registration, domain deletion/redemption) are missing, and the sheer sprawl makes coverage hard to verify.

Resources