Skip to main content
Glama

Grant wiki access

wiki_grant
Destructive

Give one person or one team a level on a wiki: read (reads), write (also writes pages and records) or admin (also removes pages, and changes who has access). A grant already held is replaced, so this is also how a level changes. Requires an admin of the wiki or an organization owner. Recorded in the organization's audit log as made by the person you act for, through you.

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": {
      "wiki": "<wiki>",
      "kind": "<kind>",
      "id": "<id>",
      "level": "<level>",
      "org": "<org>"
    },
    "name": "wiki_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe person's user id (members_list) or the team's id (team_list): user_2abc, team_9xyz. Never a name, a slug or an email.
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
kindYesWhether the grant is to one person (user) or to a team.
wikiYesThe wiki's name, without a colon or a path (general).
levelYesThe level to give.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With annotations already declaring destructiveHint=true and openWorldHint=false, the description still adds real context: existing grants are replaced, admin-level grants can strip access and change other people's permissions, admin/owner authorization is required, and the action is audited as performed by the impersonated user. It does not state whether revocation via wiki_revoke is the cleaner path or what happens on partial failure, leaving some behavioral gaps for a destructive write.

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 tight sentences, front-loaded with the operation and levels, then the replacement semantics and permissions. The parenthetical level definitions are denser than necessary but each clause carries information; no filler.

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 destructive, no-output-schema mutation with five required params, the description covers the effect on existing grants, authorization, auditing and level meanings. It could say more about failure modes or how existing access is replaced (per person vs. per team), but an agent has enough 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 the baseline is 3; the description does add value by defining what each level implies (read reads, write writes pages and records, admin also removes pages and manages access). It adds nothing about id format, org, or wiki naming, but the schema already covers those thoroughly.

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 resource ("Give one person or one team a level on a wiki") and enumerates the three levels with their semantics, which cleanly distinguishes it from wiki_revoke, wiki_remove and access_* siblings. An agent can identify the operation without opening the 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?

Makes the key routing point explicit: "A grant already held is replaced, so this is also how a level changes," which tells the agent there is no separate update path to hunt for. It also states prerequisites ("Requires an admin of the wiki or an organization owner") but names no exclusion cases or sibling alternatives by name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources