Skip to main content
Glama

commsharbor

Commsharbor email trial activate

commsharbor_email_trial_activate

Start the free receive-only Trial for 7 days, once per organization: 1 GB shared storage, unlimited mailboxes and no outgoing SMTP or external filter forwarding. No card, renewal or charge. After 7 days, writes without a paid plan answer 402 email_trial_expired. Requires a new workspace and operator-proved native quota. 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>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "commsharbor_email_trial_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idempotency_keyYesStable key for this request
organization_idYesOrganization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses post-expiry behavior (writes without a paid plan return 402 email_trial_expired), that no card, renewal or charge is involved, the resource limits (1 GB shared, unlimited mailboxes, no outbound SMTP), and that the service credential stays server-side and mailbox passwords/message content are never returned. For a non-readOnly mutation flagged idempotentHint=false, this is unusually rich context.

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?

Front-loaded with the action and duration, and every sentence carries a concrete fact. It is dense to the point of reading as a run-on of clauses (quotas, expiry, permissions, credential handling) that could be grouped more crisply, but nothing 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?

For a two-parameter mutation with no output schema, the description covers preconditions, quotas, expiry consequences and permission model thoroughly. It omits what the call actually returns (trial state, workspace binding) and does not point to a concrete upgrade sibling, which are the remaining gaps.

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 both organization_id and idempotency_key are already documented in the schema; baseline 3 applies. The description adds only the 'once per organization' scoping hint for organization_id and says nothing about the required idempotency key's purpose or reuse semantics.

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?

States a specific verb and resource ('Start the free receive-only Trial') plus the defining scope constraints: 7 days, once per organization, receive-only, 1 GB storage. An agent can immediately tell this apart from sibling tools like email_plans or billing_catalog without opening either schema.

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?

Gives clear preconditions ('once per organization', 'requires a new workspace and operator-proved native quota') and exclusions ('no guest access', members read-only, owners/admins/org keys manage). It implies the paid-plan path via the 402 email_trial_expired case but never names a sibling tool such as commsharbor_email_plans as the upgrade alternative, so routing is left partly to inference.

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.