Skip to main content
Glama

OSIR Domain Registrar

by com.osir

listCategorizedTlds

List TLDs from the OSIR catalog that have category and audience metadata populated. Returns structured candidates only — no ranking, no scoring.

USAGE PATTERN:

  1. Call this tool with optional structured filters (price cap, exclude ccTLDs, exclude restricted, etc.) based on what the user said.

  2. Examine the returned candidates. Each has categories and audience arrays you can match against the user's keywords and intent.

  3. Pick 3-6 TLDs based on relevance to the user's project. Show your reasoning to the user.

  4. Pass the chosen TLDs to bulkDomainSuggestions to find specific names.

The categories vocabulary is controlled. Common values include: generic, business, commerce, tech, dev, ai, software, web, mobile, api, cloud, data, health, medical, pharma, clinical, wellness, fitness, dental, finance, fintech, banking, education, academic, media, news, design, art, creator, agency, community, social, blog, nonprofit, personal, brand, marketplace, retail, music, audio, video, photo, startup, infrastructure, journal.

The audience vocabulary includes: b2c, b2b, professional, developer, creator, enterprise, smb, consumer, startup.

Note: registrationPrice and renewalPrice in each candidate are decimal strings (e.g. "10.39"), not numbers.

When the user's request is budget-conscious, set maxRegisterPrice. When they explicitly say "no country domains", set excludeCcTLDs=true. When they mention regulated industries casually (without intent to register a restricted TLD), set excludeRestricted=true.

Do NOT set excludePremium as a budget filter. hasPremium=true means the TLD has registry-level premium pricing for a small subset of names — the standard registrationPrice shown in the catalog applies to most names. .app, .dev, and .tech are all hasPremium=true but register most names at their standard price. Only set excludePremium=true when the user explicitly asks for "no premium domains" or "no surprise pricing."

Auth: not required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
registryNo
excludeCcTLDsNo
excludePremiumNo
maxRegisterPriceNo
excludeRestrictedNo

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden, and it delivers: auth not required, output is structured candidates only, no ranking/scoring, prices are decimal strings, and hasPremium semantics are explained to prevent misinterpretation. It also clarifies what excludePremium does not mean.

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?

Long but well organized with a front-loaded purpose sentence, a numbered workflow, controlled vocabulary lists, and price-format note. Every section earns its place, and there is no repetition of schema fields or fluff.

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 tool with no output schema and no annotations, the description explains the return shape (candidates with categories and audience arrays), the pricing format, the intended workflow, and the meaning of each important filter. The only real gap is the unexplained registry parameter, which is minor against the overall completeness.

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?

With 0% schema description coverage, the description compensates strongly by explaining maxRegisterPrice, excludeCcTLDs, excludeRestricted, and excludePremium with concrete triggers. However, the registry parameter is never explained, leaving one of five parameters without semantic guidance.

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?

States a specific verb and resource: 'List TLDs from the OSIR catalog that have category and audience metadata populated.' It also explicitly contrasts itself with ranking/scoring tools, and the usage pattern names bulkDomainSuggestions as the downstream sibling, so an agent can distinguish it from nearby tools.

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?

Provides a numbered usage pattern with explicit next steps, plus conditional filter guidance: maxRegisterPrice for budget-conscious users, excludeCcTLDs for 'no country domains', excludeRestricted for casual mentions of regulated industries, and clear when-not-to-use guidance for excludePremium. This is unusually actionable and complete.

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

B3.1/5.0
Disambiguation2/5

The set has several near-duplicate or heavily overlapping tools: initiateTransfer and transferDomain appear to do the same thing, and generateDomainSuggestions, bulkDomainSuggestions, suggestAlternatives, spinDomainWords, and addPrefix/addSuffixToDomain all occupy suggestion space. Account/profile tools like getAccountSummary, getMyProfile, getRecentActivity, and getMyAuditLogs also blur together.

Naming Consistency2/5

Many tools follow verb_noun camelCase (createDnsRecord, listInvoices, updateContact), but the broader set mixes styles: osirAppCreateUpload vs osirAppList vs osirAppStatus, plus inconsistent verbs like check/verify/validate/preview for similar lookup actions. The naming is readable but not predictable across the full surface.

Tool Count1/5

105 tools is an extreme count for any single MCP server, even one spanning domain registration, DNS, VPS, email, billing, app deployment, and site publishing. The surface would be far more coherent split into focused servers by domain.

Completeness3/5

Core domain, DNS, billing, VPS, mail, and app deployment workflows are broadly covered. However, there are notable gaps: no way to update or reassign the contacts on an existing domain, no update operation for host/glue records, and no VPS power operations like reboot or stop outside the external control panel.

Resources