Skip to main content
Glama

get_acl

Read-only

Retrieves full ACL rule details—script, decision type, and required roles—and flags any required role that no longer exists. Use it to audit access control rules by ACL sys_id.

Instructions

Get full details of an ACL rule including its script, decision type and required roles (required_roles flags any role that no longer exists)

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": {
      "sys_id": "<sys_id>"
    },
    "name": "get_acl"
  }
}

Input Schema

NameRequiredDescriptionDefault
sys_idYesACL sys_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description still adds genuine behavioral context by disclosing that required_roles flags roles that no longer exist, which tells the agent the payload can contain stale references. It does not cover failure behavior for an invalid or missing sys_id.

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?

A single front-loaded sentence with the payload fields enumerated immediately, plus one parenthetical that carries the most useful behavioral detail. No filler, though the parenthetical is slightly awkward and could be a separate clause.

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 necessary work of naming the returned fields (script, decision type, required roles), and read-only annotations cover safety. What remains thin is edge behavior: what happens when sys_id does not resolve to a rule.

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?

Only one parameter (sys_id) at 100% schema description coverage, so the schema already carries the semantics. The description adds no format or sourcing detail for sys_id, which is acceptable at this coverage level but is the baseline rather than added value.

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?

States a specific verb and resource (get full details of an ACL rule) and enumerates what comes back: script, decision type, required roles. An agent can distinguish it from create_acl/update_acl/get_acl_posture by the fact that it retrieves one rule's full body, though the description never names those siblings explicitly.

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 only implied: 'Get full details' suggests calling it when a summary or list view is insufficient, and the required sys_id implies a known identifier. There is no explicit when-to-use, no when-not-to-use, and no pointer to get_acl_posture for posture-level questions or to a search/list tool for discovery.

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

Deploy Server

Other Tools