Skip to main content
Glama
Sign In

Dock

by ai.trydock
OverviewDiscussionsAdmin

share_workspace

Add someone to a workspace at a specified role: a human by email, or an agent by agent_id. For an email that already belongs to a Dock user, they're added immediately and a notification email is sent; otherwise a 7-day invite token is minted that auto-accepts on magic-link sign-in. An agent_id (the agent's Dock id, or its agt_ id) adds that agent directly as a member, never as an invite; the agent must be in the workspace's org and not archived. Editor role required on the workspace. Emits member.joined (added) or member.invited (invited). Use update_workspace_member to change a role afterwards, remove_workspace_member to remove a member or revoke a pending invite.

Input Schema

NameRequiredDescriptionDefault
roleNoRole to grant. Defaults to `editor`. Owner-tier transitions require an owner caller.
slugYesThe workspace slug. Accepts either the bare slug ('my-workspace') or the org-prefixed form ('my-org/my-workspace') as shown in the dashboard URL; both resolve to the same workspace.
emailNoEmail address of the human to invite. Pass this or `agent_id`, not both.
agent_idNoAdd an agent directly: its Dock id, or its agt_ id. Pass this or `email`, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "Add an agent directly: its Dock id, or its agt_ id. Pass this or `email`, not both.",
+  "type": "string"
+}
    • changedInput schema / properties / email / description
      Previous value: -"Email address of the human to invite."New value: +"Email address of the human to invite. Pass this or `agent_id`, not both."
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "email"
-]New value: +[
+  "slug"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The workspace slug. Accepts either the bare slug ('my-workspace') or the org-prefixed form ('my-org/my-workspace') as shown in the dashboard URL — both resolve to the same workspace."New value: +"The workspace slug. Accepts either the bare slug ('my-workspace') or the org-prefixed form ('my-org/my-workspace') as shown in the dashboard URL; both resolve to the same workspace."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: existing Dock users are added immediately with a notification email, non-users get a 7-day invite token that auto-accepts on magic-link sign-in, agents are never invited and must be in the workspace's org and not archived. It also names the emitted events (member.joined, member.invited) and the permission gate.

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?

Purpose is front-loaded in the first clause and essentially every sentence carries distinct information. The middle is dense with semicolon-chained clauses, which slightly hurts scannability, but nothing is filler.

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 4-parameter mutation tool with no annotations and no output schema, the description covers prerequisites, side effects, and outcome states. It stops short of describing the response payload (e.g., whether a member object or invite token is returned), which is a minor 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?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning beyond the schema by explaining what each identity parameter actually triggers (immediate membership vs invite token; agent added directly, never invited). It does not restate the slug or role enum semantics, which the schema already covers.

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?

The opening clause gives a specific verb and resource ('Add someone to a workspace at a specified role') and immediately branches on the two identity types (email vs agent_id). An agent can distinguish this from update_workspace_member or remove_workspace_member without opening any schema.

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?

Explicit routing is provided: use update_workspace_member to change a role afterwards, remove_workspace_member to remove a member or revoke a pending invite. It also disambiguates parameter choice ('a human by email, or an agent by agent_id') and states the caller prerequisite (Editor role required).

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