Skip to main content
Glama

Nuntior

by com.nuntior.mcp
OverviewDiscussionsAdmin

Register Agent Account & Workspace

account_register

Provision a new Nuntior user account, multi-tenant workspace, default brand profile, and live Bearer API key (ntr_live_...) in one zero-browser call. Use this tool when an AI agent or developer needs to onboard from scratch without opening a web browser first. Returns the newly created userId, workspaceId, defaultProfileId, live apiKey, and a 1-click claimUrl so a human owner can optionally claim the workspace in the web console (https://nuntior.com/app). If the email already exists, returns a fresh session key for that workspace.

Input Schema

NameRequiredDescriptionDefault
nameNoDisplay name for the human owner or autonomous agent operator (e.g. 'Alex Rivera' or 'Growth Agent').
emailNoOwner or developer email address used to identify the Nuntior account and receive workspace claim notifications (e.g. 'founder@company.com').
agentHarnessNoIdentifier of the calling AI agent harness or MCP client (e.g. 'grok-bot', 'cursor', 'claude-code', 'n8n', 'openclaw', 'windsurf') for telemetry attribution.grok-bot
organizationNameNoOrganization, agency, or workspace name used to label the multi-tenant workspace and default brand profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / agentHarness / description
      Previous value: -"Calling AI agent harness (e.g. grok-bot, cursor, claude-code, openclaw, hermes)"New value: +"Identifier of the calling AI agent harness or MCP client (e.g. 'grok-bot', 'cursor', 'claude-code', 'n8n', 'openclaw', 'windsurf') for telemetry attribution."
    • changedInput schema / properties / email / description
      Previous value: -"User or agent owner email address"New value: +"Owner or developer email address used to identify the Nuntior account and receive workspace claim notifications (e.g. 'founder@company.com')."
    • changedInput schema / properties / name / description
      Previous value: -"User or agent display name"New value: +"Display name for the human owner or autonomous agent operator (e.g. 'Alex Rivera' or 'Growth Agent')."
    • changedInput schema / properties / organizationName / description
      Previous value: -"Company or workspace name"New value: +"Organization, agency, or workspace name used to label the multi-tenant workspace and default brand profile."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the mutation and open-world profile, and the description adds valuable behavior: it lists what gets created, says the API key is live, explains the claimUrl, and covers the existing-email path. It stops short of clarifying key lifecycle details such as whether the API key is shown only once or how claim URLs expire.

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 usage condition, then return values and edge-case behavior. Every sentence carries useful information and none is wasted.

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?

With no output schema, the description appropriately explains the key return values and the existing-email behavior. A minor gap remains around what happens when optional parameters are omitted, since none of the four inputs are required.

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 already defines all four parameters well. The description adds some meaning around email reuse and workspace labeling, but most parameter-level detail still comes from the schema rather than the description.

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 and a precise set of resources: provisioning a user account, multi-tenant workspace, default brand profile, and live Bearer API key. It is immediately distinguishable from sibling tools such as account_status and accounts_manage.

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 clearly says to use this tool when an agent or developer needs browserless onboarding from scratch, and it explains the existing-email case. It does not explicitly name alternatives or state when not to use it, but the intended context is clear.

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

All Nuntior toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources