past.dev

Grant project access

grant_project_access

DestructiveIdempotent

Grants one member direct access to one project at Read, Write or Admin, optionally until a date; granting again replaces their grant. Mirrors Grant access on a project's Access tab; needs project Admin on that project. Owners and Admins already reach every project and Billing none, so they cannot be granted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userId": "<userId>",
      "level": "<level>"
    },
    "name": "grant_project_access"
  }
}

Input Schema

Name	Required	Description
`level`	Yes	Read, Write or Admin.
`userId`	Yes	The member's userId, as list_members or get_project_access returns it.
`project`	No	The project's slug; omitted, the organization's only live project.
`expiresAt`	No	When the grant ends, 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.

Changed2 schema fields changedOct 20, 2026
- changedInput schema / properties / expiresAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedInput schema / properties / project / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
First observedOct 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it explains that 'granting again replaces their grant' (the concrete destructive/idempotent behavior behind destructiveHint+idempotentHint), that the grant can be time-boxed via 'optionally until a date', and that the caller must hold project Admin. This is a mutation tool whose safety profile, replacement semantics and auth requirement are all disclosed.

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?

Purpose is front-loaded in the first clause, followed by semantics, prerequisite and exclusions in a tightly packed three-sentence block. Dense but every clause carries information; a minor cost is the semicolon-linked length of the opening sentence.

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 4-parameter mutation tool with a fully documented schema and no output schema, the description supplies the missing behavioral layer: permission requirement, replacement semantics, expiry behavior and who cannot be granted. An agent has everything needed to call it correctly.

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 coverage is 100%, so all four parameters already carry descriptions covering level values, userId source, the project slug default and the ISO 8601 expiresAt with past-date refusal. The description restates level and expiry but adds no syntax or default behavior beyond the schema, so the 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?

States a specific verb and scope: 'Grants one member direct access to one project at Read, Write or Admin'. The cardinality (one member, one project) and the level set make it distinguishable from siblings like revoke_project_grant, set_member_role and create_access_rule 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 Guidelines4/5

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

Gives the precondition explicitly ('needs project Admin on that project') and an exclusion rule ('Owners and Admins already reach every project and Billing none, so they cannot be granted'), which prevents predictable failed calls. It does not name alternative routes such as create_access_rule for group-based access, so the when-to-use-vs-alternatives dimension is slightly incomplete.

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

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

Resources

Need Help?