Skip to main content
Glama

Layerz

by cc.layerz.app
OverviewDiscussionsAdmin

Invite or revoke model access

layerz_share_model
Destructive

Changes who can access a model, by op. invite (default): grants email the role viewer (read-only, default) or editor; a registered user gets an active share, an unregistered one a pending invite; both receive an email. revoke: removes the collaborator or pending invite principal_id (an id from the sharing.members of layerz_get_model). Owner-only. The link visibility (invite / public) is changed by the owner in the web app only. No version is persisted. Not advertised to read-only keys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opNoinvite (default) | revoke.invite
roleNo`invite`: viewer (read-only, default) or editor.
emailNo`invite`: the email address to invite.
model_idNoTarget model UUID. Required for user-scoped API keys; validated against the bound model for model-scoped keys.
principal_idNo`revoke`: collaborator user id or pending-invite id from `sharing.members`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"The email address to invite."New value: +"`invite`: the email address to invite."
    • changedInput schema / properties / model_id / description
      Previous value: -"Target model UUID. Required for user-scoped API keys; ignored (or validated against scope) for model-scoped keys."New value: +"Target model UUID. Required for user-scoped API keys; validated against the bound model for model-scoped keys."
    • addedInput schema / properties / op
      Added value: +{
+  "default": "invite",
+  "description": "invite (default) | revoke.",
+  "enum": [
+    "invite",
+    "revoke"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / principal_id
      Added value: +{
+  "description": "`revoke`: collaborator user id or pending-invite id from `sharing.members`.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / role / description
      Previous value: -"viewer (read-only) or editor (can edit). Defaults to viewer."New value: +"`invite`: viewer (read-only, default) or editor."
    • removedInput schema / required
      Removed value: -[
-  "email"
-]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint/openWorldHint only flag risk): it discloses owner-only authorization, that a registered vs unregistered invitee produces an active share vs a pending invite, that an email is sent, that no version is persisted, and that the tool is not advertised to read-only keys.

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?

Extremely dense yet well-ordered: operation modes first, then authorization and side effects, then constraints. Every clause carries operational information with no filler.

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 5-param mutation with no output schema and only terse annotations, this covers the essentials an agent needs: mode branching, permissions, side effects, and where the revoke identifier originates. Nothing material is left to inference.

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 already 100%, but the description still adds value: it ties `role`/`email` to the `invite` branch, `principal_id` to the `revoke` branch, and explains that `principal_id` comes from `sharing.members` of `layerz_get_model`. It stops short of adding format or edge-case detail beyond the schema's enum/pattern constraints.

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 the specific verb pair (invite/revoke via `op`) and the exact resource it mutates: model collaborator access. It is clearly distinguishable from siblings like `layerz_get_model` (read) and `layerz_manage_version`, and even names `layerz_get_model` as the source of `principal_id`.

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?

Explicitly separates the two modes: `invite` (default) grants viewer/editor and mails the user; `revoke` removes a collaborator or pending invite. It also states the owner-only precondition, the `model_id` scoping rule, and that link visibility cannot be changed here, routing the agent elsewhere.

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

All Layerz toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources