Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

workspace_invite_revoke

DestructiveIdempotent

Revoke a pending invitation to the active workspace (or one named by workspace_id) so its link stops working. Requires owner or admin role. Get the invite id from workspace.invites. An invite that is already accepted, expired or revoked answers not_found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invite_idYesId of the pending invite, from workspace.invites.
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 the invite belongs to. 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.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the mutation profile is covered. The description adds meaningful context beyond them: the owner/admin authorization requirement, the concrete effect (link stops working), and the not_found outcome for invites that are already accepted, expired, or revoked.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the primary action and effect, then prerequisites, then edge-case outcome. No sentence is wasted.

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 still covers what an agent needs: required role, effect of the call, id provenance, and the failure mode. Nothing material for correct invocation is missing.

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%, so all three parameters are already documented, including the workspace_id fallback and in_workspace semantics. The description only adds the source of invite_id (workspace.invites), which largely duplicates the schema. Baseline 3 is correct when the schema carries the load.

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 (revoke) and resource (pending invitation), with the exact scope (active workspace or one named by workspace_id) and the effect (link stops working). An agent can distinguish it from sibling workspace_invite (create) and workspace_invites (list) 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 Guidelines4/5

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

Gives the prerequisite (owner or admin role), the condition (pending invites only), and where to source the id from workspace.invites. It stops short of explicitly naming alternatives, but the 'pending / not_found for accepted, expired, revoked' clause effectively routes the agent.

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