Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

workspace_invite

Invite a person to the active workspace (or one named by workspace_id) by email address. Requires owner or admin role. The backend emails them a join link and the invite expires in 7 days; the same link is returned as invite_url so you can pass it on yourself. Inviting an address that already has an account works too — they see the invitation in the app once logged in. Use workspace.invites to see what is still pending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoRole to grant on acceptance. OMIT to invite as a regular member. 'admin' additionally lets them manage members and workspace settings.
emailYesEmail address to invite.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
workspace_idNoNumeric workspace id to invite into. Omit to target the currently-routed workspace (workspace.current).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations (which only declare non-readonly, non-idempotent, non-destructive): backend emails a join link, the invite expires in 7 days, the link is echoed as invite_url for manual forwarding, and existing accounts see it in-app. These are exactly the operational facts an agent needs and cannot get from structured 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?

Well front-loaded: the action, then the authorization requirement, then the side effects, then the sibling pointer. Every sentence carries information, though the parenthetical redundantly restates the schema's workspace_id default.

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?

With no output schema, the description correctly discloses the return value (invite_url) and covers authorization, expiry, and the already-registered edge case. Nothing material is missing for correct invocation.

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?

Schema coverage is 100% and each parameter already documents itself, including the OMIT-to-default behavior for role and workspace_id. The description restates the workspace targeting and role outcome without adding syntax or format detail beyond the schema, so the baseline of 3 applies.

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 (Invite) plus resource (a person to the workspace) and the targeting mechanism (active workspace or workspace_id). It is clearly distinguishable from the sibling workspace_invites and workspace_member_update tools.

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?

Explicitly names the prerequisite (owner or admin role) and routes the agent to the sibling tool for the adjacent need: 'Use workspace.invites to see what is still pending.' It also flags the non-obvious case where the invitee already has an account.

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

All dialogbrain 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