Skip to main content
Glama

list_ai_approval_requests

Read-only

Lists AI Control Tower assessment and approval requests, with optional review tasks, reviewer, and state details. Filter by asset, state, active status, or result limit.

Instructions

List AI Control Tower assessment / approval requests (sn_ai_governance_assessment_request) and optionally their review tasks (sn_ai_governance_assessment_task) with reviewer and state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ai_approval_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoFilter by governance details sys_id
limitNoMax requests (default 50)
stateNoRequest state value: 1 Open, 3 Completed, 4 Canceled
activeNoOnly active (open) requests
include_tasksNoInclude review tasks (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context that review tasks are included by default and that reviewer and state accompany results, but says nothing about pagination, ordering, or cross-table join cost.

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 no filler, and the optional-task behavior is stated inline rather than buried. Slightly dense with two raw table names but each element earns its place.

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?

Five optional parameters, full schema coverage, and no output schema; the description tells the agent what entity is listed and what accompanies each record. Adequate for a read-only lister, though it omits ordering and pagination expectations.

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 every parameter already carries a description, so the schema does the heavy lifting. The description adds no syntax or default detail beyond what the schema states (e.g. the state enum and the include_tasks default are already in the schema).

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?

Names a specific verb and resource and pins it to concrete tables (sn_ai_governance_assessment_request / sn_ai_governance_assessment_task), which distinguishes it from generic sibling listers like list_approvals or list_assessments without requiring a schema read. It does not explicitly name a sibling it is not, so it stops short of the top score.

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

Usage Guidelines2/5

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

Provides no when-to-use or when-not-to-use guidance and never points to alternatives such as list_approvals or list_assessments. The only usage hint is the parenthetical 'optionally their review tasks', which describes a parameter rather than the tool's place among siblings.

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