Skip to main content
Glama

past.dev

by dev.past
OverviewDiscussionsAdmin

Create an access rule

create_access_rule

Creates a tag-matched rule: the groups and people it names reach every live project its tags match, at its level, until it lapses. Mirrors New rule on Settings › Roles & access; needs Owner or Admin. Name at least one group or person, and give tags unless match is Every. Call preview_access_rule first and tell the person what it would reach.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoThe tags to match; required unless match is Every.
levelYesRead, Write or Admin.
matchYesAll (the project carries every tag), Any (at least one), or Every (every live project, whatever it carries).
userIdsNoPeople by userId, as list_members returns it.
groupIdsNoGroup ids, as list_access_groups returns them.
expiresAtNoWhen the rule lapses, as an ISO 8601 date or time in the future; omitted, it never does. A date already past is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / expiresAt / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / groupIds / items / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / groupIds / type
      Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
    • changedInput schema / properties / tags / items / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / tags / type
      Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
    • changedInput schema / properties / userIds / items / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / userIds / type
      Previous value: -"array"New value: +[
+  "array",
+  "null"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, non-destructive, non-idempotent, closed-world). The description adds non-obvious context the annotations cannot: it requires Owner/Admin, the rule persists 'until it lapses', and it affects 'every live project its tags match'. It does not restate idempotency or destructive semantics, but that is covered by annotations.

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?

Three sentences, front-loaded with what the tool creates before moving to prerequisites and the preview workflow. Dense but largely waste-free; the 'Mirrors New rule on Settings › Roles & access' clause is useful orientation but slightly redundant with the rest.

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 mutation tool with no output schema and full schema coverage, the description covers everything an agent needs: effect scope, auth requirement, required-input constraints, expiry behavior, and the mandatory preview step. No meaningful gap remains.

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 baseline is 3. The description goes beyond the schema by surfacing a constraint the schema does not encode: though only match and level are marked required, at least one of groupIds/userIds must be supplied, and tags are needed unless match is Every. That is genuine added meaning, not repetition.

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 (Creates) and resource (tag-matched rule) and explains the actual semantics: named groups/people reach every live project matching the tags, at the given level, until expiry. This clearly distinguishes it from create_access_group, update_access_rule, and delete_access_rule, and the UI mirror ('New rule on Settings › Roles & access') anchors it further.

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 prescribes the workflow ('Call preview_access_rule first'), states the auth prerequisite (needs Owner or Admin), and gives the validity conditions (name at least one group or person; supply tags unless match is Every). That is when-to-use, prerequisite, and constraint guidance in one place.

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

All past.dev 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