Cloche

Get access

get_access

Read-only

Reads how an app is shared: public or private, every live share link (ids only, never URLs), and every invited person under grants. For when the person asks who can open an app. Giving someone a link means making a new one. A person appears by invite address until they sign in, then by account id; either works for revoke-grant.

Input Schema

Name	Required	Description	Default
`app_id`	Yes	the app to read sharing for

Output Schema

Name	Required	Description
`links`	Yes	every share link that still opens this app, newest first, each without its address, which is given only when the link is made; empty means none do
`access`	Yes	"public" if anyone with the app's own address can open it, "signup" if anyone who signs up can, otherwise "private"
`folder`	No	the folder this app is in, and who it lets open the app too; changed on the folder in Cloche, never with set_access
`grants`	Yes	every person invited by id or email, with what each can do; each subject_or_email is what set_access "revoke-grant" takes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / folder

Added value: +{
+  "additionalProperties": false,
+  "description": "the folder this app is in, and who it lets open the app too; changed on the folder in Cloche, never with set_access",
+  "properties": {
+    "access": {
+      "description": "\"public\" if anyone with the folder's link opens every app in it",
+      "type": "string"
+    },
+    "grants": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "role": {
+            "type": "string"
+          },
+          "subject_or_email": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "subject_or_email",
+          "role"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "links": {
+      "description": "live links to the folder, each opening this app",
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "access",
+    "grants",
+    "links"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

Changed1 schema field changedOct 10, 2026

changedOutput schema / properties / access / description

Previous value: -"\"public\" if anyone with the app's own address can open it, otherwise \"private\""New value: +"\"public\" if anyone with the app's own address can open it, \"signup\" if anyone who signs up can, otherwise \"private\""

First observedOct 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, yet the description still adds real behavioral value: links are returned as ids and never URLs, and a person is keyed by invite address before sign-in and by account id after. That identity-keying detail materially affects how an agent uses the result.

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?

Four short sentences, front-loaded with the return contents and the usage trigger. Every sentence contributes something, though the aside about creating a new link is the least essential of the set.

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 single-parameter read tool with an output schema, annotations covering the safety profile, and full schema coverage, nothing an agent needs is missing. The description even preempts the identity-format question that the output schema alone would not resolve.

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?

The single parameter has 100% schema description coverage ("the app to read sharing for"), so the schema already carries the meaning. The description adds no syntax, format, or constraint detail about app_id beyond what the schema states, which is the expected baseline when coverage is complete.

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?

States a specific verb and resource (reads an app's sharing state) and enumerates exactly what is returned: public/private flag, live share links as ids, and invited people under grants. That level of specificity makes it immediately distinguishable from set_access and revoke-grant.

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

Usage Guidelines4/5

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

Gives an explicit trigger: "For when the person asks who can open an app." It also routes around the write path indirectly ("Giving someone a link means making a new one") and names revoke-grant as the consumer of the returned identity form. It stops short of explicitly saying "use set_access to change sharing," so it is clear but not exhaustive.

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

All Cloche tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.