Skip to main content
Glama

List access rules

list_access_rules
Read-only

List the access rules on one connection: for each group, and for everyone else, which tables are allowed or hidden, hidden and masked columns, row filters and AI limits, in the order they apply. Needs an active Guard approval; see request_guard_edit.

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": {
      "connectionId": "<connectionId>"
    },
    "name": "list_access_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdYesConnection id from list_connections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context not in the annotations: the approval prerequisite and the fact that rules are returned "in the order they apply", which matters for interpreting precedence.

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

Conciseness5/5

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

The verb and scope are front-loaded, followed by a dense enumeration of exactly what is returned, then a one-clause prerequisite. With no output schema, every clause in that enumeration earns its place; nothing is redundant.

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?

For a one-parameter read-only tool with no output schema, the description supplies the missing return-value detail (what categories of rule are included, ordering) plus the auth prerequisite. An agent has everything it needs to decide to call it and to interpret the result.

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% and the single connectionId parameter is documented as coming from list_connections. The description only restates the constraint that the listing is scoped to "one connection", adding no syntax or format detail 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.

Purpose5/5

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

The description names a specific verb and resource ("List the access rules on one connection") and then enumerates the exact payload: per-group and everyone-else table allow/hide state, hidden and masked columns, row filters, and AI limits. That is far more specific than the sibling name list_access_rules alone and clearly separates it from mutators like save_access_rules or delete_access_rules.

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 states a hard precondition ("Needs an active Guard approval; see request_guard_edit"), which routes the agent to the correct sibling before calling. It stops short of explicitly contrasting with save_access_rules or delete_access_rules, but the read-only framing plus the prerequisite pointer gives clear, actionable context.

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