Charming

unshare_app

Destructive

Revoke another user's access to one of your apps — removes a pending invitation or an accepted collaborator grant. Use this when the user wants to withdraw an invitation or remove a collaborator. Takes effect immediately for new requests. Idempotent: revoking a grant that does not exist is a no-op.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`app_id`	Yes	The app ID (UUID) to revoke access on
`grantee`	Yes	The grantee's Charming handle or account email

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Indicates success. Errors arrive as content with isError:true.
`removed`	Yes	True when a pending invitation or active grant was removed; false when there was nothing to remove (idempotent no-op).
`advisories`	No	Structured non-fatal advisories, including authoring issues and unread staff feedback responses. Each advisory.summary is also appended to the text content for the LLM path.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

addedOutput schema / properties / advisories

Added value: +{
+  "description": "Structured non-fatal advisories, including authoring issues and unread staff feedback responses. Each advisory.summary is also appended to the text content for the LLM path.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "data": {
+        "additionalProperties": {},
+        "description": "Kind-specific structured payload. Shape varies per advisory kind.",
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "doc_url": {
+        "description": "Optional docs pointer for this advisory kind.",
+        "type": "string"
+      },
+      "kind": {
+        "description": "Stable advisory identifier (e.g. \"legacy-bridge\").",
+        "type": "string"
+      },
+      "severity": {
+        "description": "Severity; omitted advisories are treated as 'info'.",
+        "enum": [
+          "info",
+          "warn"
+        ],
+        "type": "string"
+      },
+      "summary": {
+        "description": "Agent-facing summary. Self-sufficient; no extra context required.",
+        "type": "string"
+      },
+      "userSummary": {
+        "description": "End-user-facing summary. Set when the advisory should render in-app.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "summary"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedJul 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the mutating and destructive nature is known. The description goes further by disclosing that effects take effect immediately for new requests and that the operation is idempotent (revoking a non-existent grant is a no-op). These details are not in the annotations or schema, adding genuine behavioral context that helps the agent anticipate outcomes.

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?

The description is three sentences, tightly packed with purpose, usage, and behavior. It front-loads the primary function, then the usage condition, then the two key behavioral traits (immediacy and idempotency). No wasted words or redundant phrasing.

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 simple two-parameter tool with an existing output schema, the description covers all necessary aspects: what it does, when to use it, how it behaves, and edge cases (idempotency). Combined with the annotations and schema, an agent has everything needed to call it correctly and interpret results.

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 description coverage is 100%, so both app_id and grantee are documented in the schema. The description adds context about app ownership ('one of your apps') that is not present in the schema's parameter description, clarifying that the app must belong to the caller. This goes beyond the schema and adds value, though it does not elaborate on grantee specifics beyond what the schema already states.

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 description states a clear, specific verb and resource: revoking another user's access to an app. It explicitly distinguishes between revoking a pending invitation and an accepted collaborator grant, making the tool's scope unambiguous. The title 'Revoke App Share' reinforces the purpose without adding new information.

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?

The description explicitly tells when to use the tool: 'Use this when the user wants to withdraw an invitation or remove a collaborator.' This is a direct, actionable condition that leaves no ambiguity about when to invoke it. While it does not name an alternative tool, no sibling provides the same functionality (share_app is the opposite, but the description doesn't need to state that since this is the only revoke tool).

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

All Charming tools Inspect

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.