OSIR Domain Registrar

verifyAccount

Idempotent

verifyAccount: Verify a newly created OSIR account with the code from the verification email; step 2 of onboarding, no authentication required. The code is the same token as the email link, so the principal can relay it to their agent. On success the account becomes ACTIVE and billable actions are unlocked. If the code expired, call createAccount again with the same email to get a fresh one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	Verification code from the email sent by createAccount.
`accountId`	Yes	Account identifier returned by createAccount.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 3, 2026

addedInput schema / properties / accountId / description

Added value: +"Account identifier returned by createAccount."

addedInput schema / properties / code / description

Added value: +"Verification code from the email sent by createAccount."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "nextSteps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that success activates the account and unlocks billable actions, that the code is the same token as the email link, and what to do on expiry. These are meaningful behavioral details not captured by readOnlyHint, idempotentHint, or destructiveHint.

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 compact and front-loaded: purpose first, then context, then consequences, then recovery path. Every sentence adds necessary information with no filler or repetition.

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?

The description fully covers the onboarding workflow, authentication requirements, side effects, and error recovery. With an output schema present and only two well-documented parameters, nothing essential is missing for correct tool invocation.

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?

The input schema already covers both parameters fully, so the baseline is 3. The description adds useful semantic context by explaining that the code is the same token as the email link and can be relayed by the principal, which clarifies the relationship between code, email, and accountId.

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 clearly states the specific action ('Verify a newly created OSIR account'), the required input (code from verification email), and the exact onboarding context (step 2). This distinguishes it from sibling tools like verifyMailDns without ambiguity.

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 says when to use it ('step 2 of onboarding'), notes that no authentication is required, and provides an alternative for the expired-code case ('call createAccount again with the same email'). This gives the agent clear routing and recovery guidance.

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.