OSIR Domain Registrar

createContact

createContact: Create a new contact for use with domain registrations. Requires authentication. Returns the created contact including its id for assignment to domains.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	Yes	City name.
`email`	Yes	Contact's email address.
`phone`	Yes	Phone number in '+CC.number' format, e.g. '+1.5551234567'.
`state`	No	State, province, or region, if applicable.
`country`	Yes	Country as a 2-letter ISO 3166-1 alpha-2 code, e.g. 'US'.
`street1`	Yes	First street address line.
`street2`	No	Second street address line, if needed.
`lastName`	Yes	Contact's last name.
`firstName`	Yes	Contact's first name.
`postalCode`	Yes	Postal or ZIP code.
`sessionKey`	No	Session key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.
`organization`	No	Organization or company name, if any.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 3, 2026
- addedInput schema / properties / city / description
```
Added value: +"City name."
```
- addedInput schema / properties / country / description
```
Added value: +"Country as a 2-letter ISO 3166-1 alpha-2 code, e.g. 'US'."
```
- addedInput schema / properties / email / description
```
Added value: +"Contact's email address."
```
- addedInput schema / properties / firstName / description
```
Added value: +"Contact's first name."
```
- addedInput schema / properties / lastName / description
```
Added value: +"Contact's last name."
```
- addedInput schema / properties / organization / description
```
Added value: +"Organization or company name, if any."
```
- addedInput schema / properties / phone / description
```
Added value: +"Phone number in '+CC.number' format, e.g. '+1.5551234567'."
```
- addedInput schema / properties / postalCode / description
```
Added value: +"Postal or ZIP code."
```
- addedInput schema / properties / state / description
```
Added value: +"State, province, or region, if applicable."
```
- addedInput schema / properties / street1 / description
```
Added value: +"First street address line."
```
- addedInput schema / properties / street2 / description
```
Added value: +"Second street address line, if needed."
```
First observedSep 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond annotations (readOnlyHint=false, etc.), the description adds that authentication is required and that the created contact is returned including its id for assignment to domains. This is useful behavioral information not otherwise conveyed by annotations alone.

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 two compact sentences with no fluff. The primary purpose is front-loaded, followed by auth requirement and return value. Every sentence earns its place.

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?

The description covers purpose, auth, and the key return value (the id). With no output schema, mentioning the id is valuable. Minor gap: it doesn't describe the full return structure or any side effects, but the schema handles parameter details.

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 100%, so the baseline is 3. The description does not add any parameter-level detail beyond what the schema already provides, and that is acceptable given the thorough schema descriptions.

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 (create), resource (contact), and purpose ('for use with domain registrations'). This clearly distinguishes it from contact-related siblings like updateContact, deleteContact, getContact, and listContacts.

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 provides clear context: creating a contact for domain registrations, and it explicitly notes that authentication is required. It doesn't explicitly name alternatives or exclusions, but the create-vs-update/delete role is obvious from the verb and resource.

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 tools Inspect

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.

createContact

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources