Skip to main content
Glama
Sign In

EaseWeb

by host.easeweb
OverviewDiscussionsAdmin

Change access

set_access

Change the access of your presentation: "level" -- "open" (every signed-in person and agent reads and edits; the history keeps every change), "public" (everybody reads, those given access edit) or "private" (only those given access); "revoke" -- usernames whose access is taken away.

Input Schema

NameRequiredDescriptionDefault
slugYesThe presentation's slug (its address: /movie/<slug>/).
levelNoNew access level: "open", "public" or "private".
revokeNoUser names whose access is taken away.

Output Schema

NameRequiredDescriptionDefault
levelYesopen, public or private: the presentation's own level.
grantsNo
project_levelNoThe level of its project, if any.
effective_levelNoThe level that counts (the project's one when stricter).
pending_requestsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / pending_requests / items / properties / title / description
      Added value: +"Its title; null while you may not see it (a private one you asked for)."
    • changedOutput schema / properties / pending_requests / items / properties / title / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed6 schema fields changed
    • addedOutput schema / properties / effective_level
      Added value: +{
+  "description": "The level that counts (the project's one when stricter).",
+  "type": "string"
+}
    • changedOutput schema / properties / level / description
      Previous value: -"open, public or private."New value: +"open, public or private: the presentation's own level."
    • changedOutput schema / properties / pending_requests / items / properties / presentation / description
      Previous value: -"Slug of the presentation."New value: +"Slug of the presentation (null: a project)."
    • changedOutput schema / properties / pending_requests / items / properties / presentation / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedOutput schema / properties / pending_requests / items / properties / project
      Added value: +{
+  "description": "Slug of the project, for access to all of it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / project_level
      Added value: +{
+  "description": "The level of its project, if any.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. Changed3 schema fields changed
    • addedInput schema / properties / level / description
      Added value: +"New access level: \"open\", \"public\" or \"private\"."
    • addedInput schema / properties / revoke / description
      Added value: +"User names whose access is taken away."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "grants": {
+      "items": {
+        "properties": {
+          "role": {
+            "type": "string"
+          },
+          "since": {
+            "description": "ISO 8601 date and time.",
+            "type": "string"
+          },
+          "user": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "level": {
+      "description": "open, public or private.",
+      "type": "string"
+    },
+    "pending_requests": {
+      "items": {
+        "properties": {
+          "agent": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "created_at": {
+            "description": "ISO 8601 date and time.",
+            "type": "string"
+          },
+          "id": {
+            "type": "integer"
+          },
+          "message": {
+            "type": "string"
+          },
+          "presentation": {
+            "description": "Slug of the presentation.",
+            "type": "string"
+          },
+          "role": {
+            "description": "view or edit.",
+            "type": "string"
+          },
+          "status": {
+            "description": "pending, approved or declined.",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "user": {
+            "description": "Who asks.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "level"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false; the description adds real semantic content beyond that — what 'open' actually grants (edit rights for all signed-in users and agents, with full history retention), the public read/edit split, and that 'revoke' removes named users. It does not disclose required permissions or whether a level change is reversible, which is the remaining gap for a mutation tool.

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?

Front-loaded with the action and resource, then the parameter semantics in a single dense sentence with no filler. The heavy quoting and inline parentheticals make it slightly harder to scan than a bulleted breakdown would be, but nothing 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?

An output schema exists, so return values need not be explained. With all three parameters documented in the schema and the enum consequences spelled out here, an agent has everything required to invoke it correctly; only secondary details like permission requirements are absent.

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, but the description genuinely adds meaning the schema lacks: it defines the consequences of each enum value rather than restating 'open, public or private'. The revoke parameter is described only as 'usernames whose access is taken away', which mirrors the schema without adding much.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Change the access of your presentation') and enumerates the two mutation modes, so an agent can distinguish it from get_access or request_access. It stops short of naming the read-side siblings explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the verb-plus-modes framing: use this to modify access levels or revoke named users. There is no explicit when-to-use vs. when-not guidance, and no mention of the prerequisite that the caller presumably must be an owner or admin — the agent must infer it from the sibling set (get_access, answer_access_request).

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

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