Skip to main content
Glama

Who can use a wiki

access_wiki
Read-only

Who has access to one wiki, at what level, and why: its visibility (org: open to everyone in the organization; restricted: grants only), the teams it is granted to with each one's level (read, write or admin) and member count, and every person who holds it for a reason of their own, with their role, level and reasons (via: org, a grant to them as user, a team they are on, or owner of the organization). On a wiki open to the organization, everyoneLevel is what every member holds, and people who hold it only because everyone does are counted (members), not listed. An owner with level null sees the wiki's access but not its content. Answers only for a wiki the caller may see.

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>",
      "org": "<org>"
    },
    "name": "access_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it.
wikiYesThe wiki's name, without a colon or a path (general).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / org / description
      Previous value: -"slug of the organization whose people, teams and access to read. Required on every call, even when only one organization is listed; a path never names it."New value: +"slug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes well beyond that by explaining the everyoneLevel semantics on org-open wikis, that inherited holders are counted rather than listed, that an owner with null level sees access but not content, and that results are scoped to wikis the caller may see. These are non-obvious behavioral rules an agent could not derive from the schema or annotations, though output shape/pagination isn't discussed.

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?

The core answer ('who has access, at what level, and why') is front-loaded, followed by the enumeration of what is returned. It is a long, heavily nested sentence with several parenthetical asides, which costs some readability, but nearly every clause carries distinct information rather than filler.

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?

With no output schema, the description must carry the return semantics, and it does: it enumerates visibility, team grants with levels and counts, individual holders with roles and via-reasons, and the everyoneLevel edge case. The caller-scoping note closes the remaining gap, leaving nothing essential unexplained for a two-parameter read tool.

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 description coverage is 100%, and the schema already explains both org (required slug, path never names it) and wiki (name without colon or path). The description adds only the framing 'one wiki', so the schema is doing the heavy lifting and the baseline of 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?

The description names a specific resource (one wiki's access) and a specific payload (visibility, team grants with levels and member counts, individual holders with roles and reasons). It is clearly distinct from siblings such as access_person, wiki_grant, and wiki_revoke, which operate on a person or mutate grants rather than reporting a wiki's consolidated access picture.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the read path for 'who can see this wiki' and that wiki_grant/wiki_revoke are the mutating counterparts, but the description never says when to prefer it over access_person or what prerequisites apply. No explicit exclusions or alternative routing are given.

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