Skip to main content
Glama

Tommos

Add a domain to a company

add_a_domain_to_a_company
Idempotent

Add a second domain to a company, as the signed-in person, as the company's page does: from then, the people with an address on that domain and no link by hand belong to the company, and the answer says how many joined. A domain names one company: when another company holds it, the answer refuses and names that company (holder). A free-mail domain, one of the workspace's own people, or no domain is refused in words. The domain is a line of the company's history and of the audit trail.

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": {
      "company_id": "<company_id>",
      "domain": "<domain>"
    },
    "name": "add_a_domain_to_a_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain, as example.com
company_idYesThe company's id (from list_companies)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the real side effect: people with an address on that domain and no manual link automatically join the company, and the response reports how many joined. It also documents refusal behavior (naming the holding company as 'holder') and that the change is recorded in company history and the audit trail — none of which the annotations convey.

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 and side effect are front-loaded in the first sentence, and the refusal rules follow logically. Some phrasing is ornate ('as the company's page does', 'refused in words', 'a line of the company's history'), which costs a little density but not comprehension.

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 definition covers effect, refusals, and audit consequences, and it describes what the response reports. It leaves out authorization requirements (what role may add a domain) and whether the effect on newly joined people is reversible.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real constraint semantics for 'domain': it must be a domain only one company holds and cannot be a free-mail domain, which goes beyond the schema's 'as example.com'. The company_id parameter is only indirectly explained.

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 specific verb and resource ('Add a second domain to a company') and clarifies the scope is a second domain added on behalf of the signed-in person. It does not name or differentiate against the closest sibling, add_a_sending_domain, so an agent must infer which of the two domain-adding tools applies.

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?

Preconditions are concrete: the company must not already be claimed by another company, and free-mail domains or a domain already used by a workspace person are refused. It stops short of explicit routing guidance (e.g. 'use add_a_sending_domain instead when you want mail sending'), so the when-not-to-use case is implied rather than stated.

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.