Skip to main content
Glama

EaseWeb

by host.easeweb
OverviewDiscussionsAdmin

Access requests

list_access_requests
Read-onlyIdempotent

"incoming" (default): requests for access to YOUR presentations (pending ones, or all with include_decided); "outgoing": the requests you (or your agents) sent and their status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directionNo"incoming" (default): requests to you; "outgoing": requests you sent.
include_decidedNoAlso return approved and declined requests.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / requests / items / properties / presentation / description
      Previous value: -"Slug of the presentation."New value: +"Slug of the presentation (null: a project)."
    • changedOutput schema / properties / requests / items / properties / presentation / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedOutput schema / properties / requests / items / properties / project
      Added value: +{
+  "description": "Slug of the project, for access to all of it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / direction / description
      Added value: +"\"incoming\" (default): requests to you; \"outgoing\": requests you sent."
    • addedInput schema / properties / include_decided / description
      Added value: +"Also return approved and declined requests."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "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": [
+    "requests"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: by default only pending requests are returned unless include_decided is set. It says nothing about ordering, limits, or pagination.

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 short, front-loaded sentences with no filler. Slightly awkward quoting and punctuation, but every clause carries information and nothing is padded.

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

Completeness3/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 no explanation, and annotations carry the safety profile. However, for a list tool sitting among 40 siblings with closely related request/access tools, the description omits the basic purpose statement and any routing, leaving the definition only minimally complete.

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%, and the description essentially paraphrases the schema text for both parameters ("incoming" default, include_decided behavior) rather than adding format or edge-case meaning. Baseline 3 is appropriate when the schema already does this work.

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

Purpose3/5

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

The description never states that this tool lists access requests in a sentence of its own; it jumps straight into the meaning of the "direction" parameter values. The tool name carries the actual purpose, and the description only clarifies scope (incoming vs outgoing). It is decipherable but the verb+resource statement is implied rather than stated, and no sibling (e.g. get_access, request_access) is distinguished.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives. An agent must infer from context whether to call this versus get_access, request_access, or answer_access_request. The "default" note for incoming is a small hint but not routing guidance.

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