Skip to main content
Glama
Sign In

OrionBI

by ai.orionbi
OverviewDiscussionsAdmin

Stop sharing a dashboard with a person

dashboard_unshare
DestructiveIdempotent

Remove ONE person from a dashboard's share list, by email — the reverse of dashboard_share. Works on a dashboard you own or can edit, for a person with an account or an emailed invitation not yet accepted, whether they could view or edit. They lose access at once, unless a group or your organization still shares it with them (the reply says so); taking a group or the organization off is done by the owner in OrionBI. If they were the last person on the list, the dashboard goes back to private. Removing never turns a paused dashboard back on. dashboard is a name, or a /d/owner/slug path.

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": {
      "dashboard": "<dashboard>",
      "email": "<email>"
    },
    "name": "dashboard_unshare"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail of the person to remove, as dashboard_share_list shows it
dashboardYesName of a dashboard you own or can edit, from dashboard_list, or its /d/owner/slug path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructive and idempotent annotations, it discloses immediate access loss, the exception when group or organization sharing still grants access, and that the reply reports that exception. It further explains that removing the last person makes the dashboard private and that removal never reactivates a paused dashboard.

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?

The essential action and one-person limitation are front-loaded, and the remaining sentences supply distinct operational edge cases without filler. It is somewhat dense for a single paragraph, and the final dashboard-format sentence duplicates information already present in the schema.

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?

For a two-parameter destructive sharing mutation, the definition covers prerequisites, supported target states, immediate effects, residual-access exceptions, privacy consequences, and interaction with paused dashboards. The note about what the reply reports partially compensates for the absence of an output schema, leaving no important selection or invocation 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%, and the final sentence largely repeats the schema's accepted dashboard name or /d/owner/slug path formats. The description nevertheless adds useful target semantics for email: exactly one person, including either an account holder or someone with an unaccepted emailed invitation, rather than a group or organization.

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 precisely states the verb, resource, scope, and identifier: "Remove ONE person from a dashboard's share list, by email." It distinguishes the operation from dashboard_share and later clarifies that group or organization sharing is outside its scope.

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?

It identifies this as the reverse of dashboard_share and gives concrete applicability conditions: the caller owns or can edit the dashboard, and the target may have an account or an unaccepted invitation. It also gives an explicit alternative for unsupported cases, stating that removing a group or organization share must be done by the owner in OrionBI.

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

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