Crow Nest

Set up or remove the company domain

company_domain_set

Destructive

Use when a company admin wants all the company's apps at the company's own address. set takes base (a subdomain like apps.acme.com) and optionally policy (auto gives every app an address, ask lets each owner turn theirs on); remove deletes it and every app address on it. Only company admins can; for anyone else the reply says who can. Replies about an app with a company address include that address.

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": {
      "action": "<action>"
    },
    "name": "company_domain_set"
  }
}

Input Schema

Name	Required	Description
`base`	No	For set: like apps.acme.com.
`action`	Yes
`policy`	No	For set. Defaults to auto.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds real value beyond them: it specifies the blast radius of 'remove' (deletes the domain and every app address on it), states the admin-only authorization requirement, and explains what the reply reveals to non-admins. It does not cover rate limits or reversibility, so not a 5.

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?

One compact paragraph covering the trigger, both actions, both parameters, authorization, and reply behavior; it is front-loaded with the usage condition. The nested parentheticals for policy make it slightly dense 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 3-parameter mutation tool with no output schema, the description covers the missing pieces: authorization outcome, deletion scope, and what replies include for apps with a company address. It lacks explicit guidance on related domain tools, which is the main remaining gap.

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?

With 67% schema coverage the baseline is 3, but the description materially explains parameter meaning beyond the schema: 'base' is a subdomain like apps.acme.com, and 'policy' semantics ('auto' grants every app an address, 'ask' lets each owner enable theirs, defaulting to auto) clarify the enum choices. The 'action' enum is only implicitly 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 states a specific verb pair and resource: setting up or removing the company's domain so all company apps live at the company's own address, with 'set' and 'remove' behavior spelled out. It does not name any of the plausible siblings (company_domain, custom_domain, buy_domain), so an agent must infer the distinction from the schema, keeping it below 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 gives a clear trigger condition ('when a company admin wants all the company's apps at the company's own address') and distinguishes the two actions, including what 'remove' destroys. It stops short of naming when to prefer it over company_domain/custom_domain or other domain siblings, so no alternatives are offered.

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

All Crow Nest tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?