Skip to main content
Glama

OSIR Domain Registrar

by com.osir

spinDomainWords

Read-onlyIdempotent

spinDomainWords: Generate domain suggestions by spinning/replacing words with similar alternatives.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLanguage code; default "eng".
nameYesComma-separated words to spin, e.g. "pizza,restaurant".
tldsNoComma-separated TLDs without leading dots, e.g. "com,net".
positionNo0-based index of the word to replace.
maxResultsNoMaximum suggestions to return; default 20.
similarityNoSimilarity threshold for replacements, 0.0-1.0.

Schema Changelog

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

  1. Changed6 schema fields changed
    • addedInput schema / properties / lang / description
      Added value: +"Language code; default \"eng\"."
    • addedInput schema / properties / maxResults / description
      Added value: +"Maximum suggestions to return; default 20."
    • addedInput schema / properties / name / description
      Added value: +"Comma-separated words to spin, e.g. \"pizza,restaurant\"."
    • addedInput schema / properties / position / description
      Added value: +"0-based index of the word to replace."
    • addedInput schema / properties / similarity / description
      Added value: +"Similarity threshold for replacements, 0.0-1.0."
    • addedInput schema / properties / tlds / description
      Added value: +"Comma-separated TLDs without leading dots, e.g. \"com,net\"."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety and side-effect profile is covered. The description adds the spinning/replacement mechanism but does not disclose return shape, pagination, or any operational limits; however, annotations lower the burden.

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 a single efficient sentence with no wasted words, front-loading the main action. It loses one point only because the leading 'spinDomainWords:' prefix largely repeats the tool name and the included metadata title.

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?

Given the 100% schema coverage and comprehensive annotations, the description covers the essential operation with minimal redundancy. The main gaps are the lack of sibling differentiation and the absence of an output schema, but the tool's purpose is simple enough that the description remains adequate.

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%, with all six parameters documented, so the description does not need to repeat parameter details. It also does not add meaningful parameter-level context beyond the general spinning/replacement idea, so the baseline score of 3 is appropriate.

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?

The description clearly identifies the action (generate), the resource (domain suggestions), and the mechanism (spinning/replacing words with similar alternatives). It is more specific than a tautology, but it does not explicitly distinguish itself from sibling tools like generateDomainSuggestions, bulkDomainSuggestions, or suggestAlternatives.

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

Usage Guidelines3/5

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

The phrase 'by spinning/replacing words with similar alternatives' implies when this tool might be appropriate, but the description gives no explicit guidance about when to choose this over other domain-suggestion siblings. There are no when-to-use or when-not-to-use statements, leaving the agent to infer routing.

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