Skip to main content
Glama

commsharbor

Commsharbor email domain setup

commsharbor_email_domain_setup
Read-onlyIdempotent

Find an existing domain. Use it before a purchase. Return its organization and domain IDs only when this exact caller can open that organization. Otherwise return existing: null. This read creates no charge or job. No guest access. Members can read. Owners, admins and organization keys can manage email. The private service credential stays on the server. Mailbox passwords and message content are never returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organization_id": "<organization_id>",
      "domain": "<domain>"
    },
    "name": "commsharbor_email_domain_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check before purchase, at most 253 characters
organization_idYesOrganization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / domain / description
      Added value: +"Domain to check before purchase, at most 253 characters"
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • removedInput schema / properties / domain / description
      Removed value: -"Domain to check before purchase, at most 253 characters"
  5. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations it adds valuable context: no charge or job is created, the permission tiers (no guest, members read, owners/admins/keys manage), scoped return semantics, and that credentials, mailbox passwords, and message content are never exposed. Some overlap with readOnlyHint ('this read creates no charge') is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and usage are front-loaded well, but the tail sentences (mailbox passwords, message content, service credential) are tangential to a domain-existence lookup and partly repeat the readOnly signal. It reads longer than needed for a two-parameter check.

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 correctly supplies return behavior ('organization and domain IDs' or 'existing: null'), the authorization condition governing that return, and safety/security context. That is enough for an agent to call and interpret this simple read tool.

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 documents both parameters (domain with 253-char bound, organization_id). The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

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 states a clear verb+resource: 'Find an existing domain' and its scoping ('only when this exact caller can open that organization'). However, it never distinguishes itself from close siblings like commsharbor_email_domain_get or commsharbor_email_domain_create, so an agent must infer the difference.

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 gives explicit timing guidance ('Use it before a purchase') which is a real call-site condition. It stops short of naming alternatives or when-not situations (e.g., vs domain_get), which keeps it from a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.