Skip to main content
Glama

add_grant

Record a person’s exact words as a grant, assigning team, project, or personal scope and optional repo areas; project grants may require approvals before taking effect.

Instructions

Keep one grant: words are the person's own words, quoted exactly as they said them (never your summary); Tares adds today's date. kind is team (every project; all is the old name), project (this project only, name it in project) or personal (what may run on the person's own machine, for the key's own person). Without kind, a project makes it a project grant and no project a team grant. areas lists the GitHub repos (owner/name) a project grant reaches into, and needs an enterprise licence: the grant then waits, not in effect, until each repo's area owner (other than the giver) calls consent_grant. A project grant from someone who is neither the project's lead nor an admin also waits for the lead (an admin, when the project has none). Without a licence a grant takes effect at once. scope is the older name of kind. Only the person's own session or the orchestrator, relaying the person verbatim, may add one.

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": {
      "words": "<words>"
    },
    "name": "add_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
areasNo
scopeNo
wordsYes
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.1/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 largely meets it: it discloses the authorization constraint (only the person's own session or an orchestrator relaying verbatim), the enterprise-licence prerequisite, and that grants can sit pending until consent_grant is called or the project lead approves. It leaves out duplicate/conflict handling and any error behavior, so not exhaustive.

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?

Every clause carries information, but it is delivered as one dense run-on paragraph with nested parentheticals (licence terms, approver rules, legacy aliases) rather than front-loaded purpose followed by parameters and then side effects. An agent must parse the whole block to extract the calling rules.

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?

For a five-parameter mutation with zero schema descriptions and no annotations, the description covers inputs, authorization, licence gating, and asynchronous approval outcomes, and an output schema exists so return values need not be explained. Remaining gaps are minor: behavior when both scope and kind are passed, and what happens on a duplicate grant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry everything, and it does: words must be the verbatim quote not a summary; kind's values (team/project/personal, plus 'all' as the old team name) are enumerated with meanings absent from the schema; project names the target project; areas takes owner/name repos and triggers the waiting state; scope is identified as the legacy name for kind. Only scope-vs-kind precedence when both are supplied is left ambiguous.

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 lede 'Keep one grant' is an imprecise verb, but the body makes clear this records a single grant composed of the person's own words, a kind (team/project/personal), an optional project, and optional repo areas, and the final sentence confirms it 'adds' one. An agent can tell what resource is created. No sibling is named as an alternative, though the siblings listed are unrelated tools, so that omission costs little.

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 concrete selection rules: kind=team covers every project, project covers this project only, personal covers the person's own machine, and omitting kind infers project vs team from whether project is set. It also states the conditional consent path (consent_grant per area owner, lead approval) versus immediate effect when no licence exists. It does not describe when this tool should be avoided, but no competing grant tool exists among the siblings.

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