Skip to main content
Glama

commsharbor

Commsharbor email workspace

commsharbor_email_workspace
Read-onlyIdempotent

Read the email workspace. We operate the mail server and webmail. Your agent manages the authorized domains and mailboxes through the existing service. Check checkout_live, domain readiness and observed sending capability. A payment or accepted job alone does not prove activation or delivery. Enterprise services can require activation on demand.

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>"
    },
    "name": "commsharbor_email_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
organization_idYesOrganization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful operational caveats about activation and delivery not being guaranteed by payment or job acceptance, plus the note that enterprise services may require activation on demand. It still does not describe the response shape or concrete workspace fields.

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?

The purpose is front-loaded and the sentences are generally short, with no large digressions. Some operational framing, such as stating that the service operates the mail server and webmail, is slightly less directly useful for invocation, preventing a 5.

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 low-complexity, one-parameter read tool with annotations covering safety, the description supplies enough business context and activation caveats to call it correctly. However, without an output schema it could more explicitly state what workspace data is returned beyond the check items it mentions.

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?

There is only one parameter, organization_id, and schema description coverage is 100%, so the schema already carries the parameter contract. The description does not add any syntax, format, or selection guidance for organization_id, making this a baseline 3 case.

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 gives a clear verb and resource ("Read the email workspace") and clarifies the scope with authorized domains, mailboxes, checkout_live, domain readiness, and observed sending capability. It does not distinguish this tool from nearby siblings such as commsharbor_email_workspace_snapshot or commsharbor_email_domain_get, so it falls short of a 5.

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 for when to use the tool: checking checkout_live, domain readiness, and observed sending capability, with the warning that payment or an accepted job alone does not prove activation. It does not explicitly name alternatives or exclusions, so sibling routing remains implicit.

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.