Skip to main content
Glama
Sign In

Dock

by ai.trydock
OverviewDiscussionsAdmin

invite_to_org

Invite someone to an organization (the team). Provide an email to invite a specific person (if they already have a Dock account they're added immediately; otherwise a magic-link invite is emailed), or omit the email to create a shareable open-link invite. Optionally set role (admin or member, default member), expires_in_days, and max_uses (open-link only). Returns whether a member was added immediately or an invite is pending, plus the accept URL for link invites. AGENTS: you may invite one person by email, as a member only, when their email domain is the same as your organization owner's (not a public mail domain like gmail.com), it is your own organization, and your owner is an owner or admin of it; open links and the admin role are refused. Tell your owner whenever you invite someone.

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": {
      "org": "<org>"
    },
    "name": "invite_to_org"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesThe organization slug.
roleNoRole to grant. Default member.
emailNoEmail to invite. Omit to create an open-link invite.
max_usesNoMax accepts for an open-link invite. Omit for unlimited.
expires_in_daysNoDays until the invite expires. Omit for no expiry (open-link) or the 7-day default (email).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it explains the two execution paths (immediate add for existing accounts, magic-link email otherwise), permission/refusal rules for agents, and the obligation to notify the owner. It also discloses what is returned, which is essential given there is no output schema.

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-loads the core action and mode split before the policy caveats, and contains no filler sentences. It is dense with parentheticals and a long AGENTS clause, which costs a little readability, but each sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers everything needed to call this five-parameter mutation correctly: mode selection, defaults, per-mode expiry behavior, agent restrictions, and the shape of the result despite the absence of an output schema. No meaningful gap remains for invite_to_org relative to its sibling member-management tools.

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 already 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: max_uses applies only to open-link invites, role defaults to member, and expires_in_days behaves differently per mode (no expiry for links, 7-day default for email).

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 ('Invite someone to an organization') and immediately distinguishes its two modes: email invite versus open-link invite created by omitting the email. The name-plus-title ambiguity around 'org' is resolved by defining it as 'the team'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit selection logic: provide an email for a specific person, omit it for a shareable open link. The AGENTS block goes further and states the exact preconditions for agent use (same domain as owner, not a public mail domain, own organization, owner is owner/admin) and what is refused (open links, admin role).

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

All Dock toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources