EaseWeb

Answer an access request

answer_access_request

Approve or decline a request for access to one of your presentations or projects. "role" may change what is given (default: what was asked for); "whole_project" gives it for every presentation of the project of that presentation.

Input Schema

TableJSON Schema

Name	Required	Description
`role`	No	"view" -- read; "edit" -- read and change.
`approve`	Yes	true approves the request, false declines it.
`request_id`	Yes	The id of the access request.
`whole_project`	No	Give the access for the whole project the presentation is in (default false: this presentation only).

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`role`	No	view or edit.
`user`	No	Who asks.
`agent`	No
`title`	No
`status`	Yes	pending, approved or declined.
`message`	No
`project`	No	Slug of the project, for access to all of it.
`created_at`	No	ISO 8601 date and time.
`presentation`	No	Slug of the presentation (null: a project).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026

changedOutput schema / properties / presentation / description

Previous value: -"Slug of the presentation."New value: +"Slug of the presentation (null: a project)."

changedOutput schema / properties / presentation / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / project

Added value: +{
+  "description": "Slug of the project, for access to all of it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / whole_project

Added value: +{
+  "description": "Give the access for the whole project the presentation is in (default false: this presentation only).",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 28, 2026

addedInput schema / properties / approve / description

Added value: +"true approves the request, false declines it."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

First observedSep 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful effect semantics (role alters what is granted; whole_project extends the grant), but says nothing about permissions required, notifications, or reversibility.

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?

Two front-loaded sentences: the core action first, then parameter clarifications. Efficient, though the parenthetical definitions are slightly redundant with schema text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and all parameters are covered by the schema. The only gap is that the description does not point to list_access_requests for obtaining a request_id, which an agent must supply.

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 description coverage is 100%, so all four parameters are already documented, including the role enum and the whole_project default. The description restates role and whole_project semantics rather than adding format or edge-case detail, so baseline 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?

The description states a specific action (approve or decline) on a specific resource (a request for access to your presentations or projects). An agent can distinguish this from siblings like set_access, request_access, and list_access_requests 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 Guidelines3/5

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

Usage is implied by the name and the mutation semantics, but the description never says when to use this versus alternatives such as set_access (direct access changes) or list_access_requests (finding a request_id). No prerequisites or workflow context are given.

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

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

Resources

Need Help?