Skip to main content
Glama

Lexicon Garden

discover_permission_sets

Discover which ATProtocol permission-set lexicon schemas cover a given set of collections and/or XRPC methods. Returns matching permission sets with their OAuth scope strings (include:<nsid>), useful for determining what OAuth scopes an application needs.

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": {
      "collections": "<collections>"
    },
    "name": "discover_permission_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodsNoOptional: List of XRPC method NSIDs your application calls (e.g., ['app.bsky.video.uploadVideo', 'com.atproto.repo.listRecords'])
collectionsYesList of collection NSIDs your application reads or writes (e.g., ['app.bsky.feed.post', 'app.bsky.actor.profile', 'garden.lexicon.example'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the return shape ('matching permission sets with their OAuth scope strings (include:<nsid>)'), which is real added value. However, it omits whether the operation is read-only, any auth requirements, and what happens when no permission set matches.

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?

Two sentences, front-loaded with the action and resource, then the return value and use case. No filler; the only slight cost is dense terminology that may not be self-evident to an unfamiliar agent.

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?

With no output schema, the description does the right thing by summarizing the returned scope strings, and the input schema is fully annotated for a simple two-parameter tool. The main remaining gap is edge-case behavior when the collection/method set matches nothing.

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 both parameters are already fully documented with examples in the schema. The description only restates 'a given set of collections and/or XRPC methods' and adds no format, matching, or combination semantics beyond the schema, so the baseline of 3 applies.

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?

Uses a specific verb ('Discover') and names the resource precisely ('ATProtocol permission-set lexicon schemas'), plus the input domain (collections and/or XRPC methods). It does not explicitly contrast itself with siblings like check_compatibility or describe_lexicon, but the OAuth-scope framing makes the intent distinguishable.

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 clear context for use: 'useful for determining what OAuth scopes an application needs,' which tells the agent this is a scope-planning lookup rather than a validation or description call. It stops short of naming when not to use it or pointing to an alternative sibling.

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