Skip to main content
Glama

read_grants

Retrieve effective permissions a person has granted an AI crew, including project and personal grants, and flag project grants waiting for another repo owner.

Instructions

What the person allows the crew to do, in their own words with the date: the grants for every project, the project's own when project is given, and your personal ones. Those in effect come first; a project grant that reaches into another person's repo is listed as waiting for that owner and is NOT in effect. Never act on a permission that is not here or in the person's own words in your session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: in-effect grants are listed first, and a project grant reaching into another person's repo is surfaced as 'waiting' and explicitly NOT in effect. That ordering and pending-state semantics are exactly the kind of context annotations would otherwise supply. It does not state permissions required to call it, but the read-only nature is evident from the name and framing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope information is front-loaded and every clause carries content, but the sentences are convoluted, especially 'the project's own when `project` is given,' which reads awkwardly. A tighter phrasing would deliver the same semantics with less parsing effort.

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

Completeness4/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 shape needn't be described. Given that, the description covers scope branches, ordering, pending/not-in-effect semantics, and the operating constraint on unlisted permissions — enough for an agent to call this correctly with one optional parameter.

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 0% for the single `project` parameter, so the description must compensate. It does explain the branch — the project's own grants when `project` is given, broader coverage when it is not — which adds genuine meaning beyond the bare string field. It is still thin on accepted values or format for `project`, so the compensation is partial.

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

Purpose4/5

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

The description conveys that this returns the person's grants/permissions ('what the person allows the crew to do') and enumerates the scope: all projects, a single project when `project` is given, and personal grants. The phrasing is oblique rather than a clean verb+resource statement, but an agent can still tell this is a read of permission records, distinct from the write-side `add_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?

It gives a clear usage rule: consult this before acting on a permission, and 'Never act on a permission that is not here or in the person's own words in your session.' That is an explicit exclusion. It stops short of naming alternatives (e.g., `add_grant` for creating grants), so routing guidance is implied rather than spelled out.

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