Skip to main content
Glama

List controls

list_controls
Read-onlyIdempotent

List the reference controls of the open control profiles (draft control specifications with stable ids such as AIGE-CTL-EVAL-002, open for technical review). All filters are optional and combine with AND: profile (a profile slug such as "evaluation-environment", or its title), layer (stack layer 1-5, primary or secondary), status (draft, in-review, stable, retired), depth (specified: written in full; derived: restates a chapter 23 seed; stub: outline with open questions) and query (words that must all appear in the id, title or objective). Returns ids for get_control, each control's profile, depth, status, layer, objective and URLs.

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_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoHow far the control is written.
layerNoStack layer, 1 to 5.
queryNoFree text over id, title and objective.
statusNoPublication status.
profileNoProfile slug or title.

Output Schema

NameRequiredDescriptionDefault
asOfYesDate the profiles were last checked against their sources.
totalYes
noticeYesIllustrative, not legal advice and not a claim of conformity.
sourceYesCanonical URL of the page this answer comes from; cite it.
datasetYesURL of the open-data document the answer was read from.
filtersYes
licenseYesLicence of the data (CC BY 4.0, attribution required).
controlsYes
profilesYesThe profiles the listed controls belong to.
dataVersionYesBody of Knowledge version of the data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description doesn't need to repeat safety. It adds real behavioral context: AND semantics across filters, the meaning of each depth tier, and the shape of the returned fields. It omits any mention of result limits or pagination, which matters for a list tool with five optional filters.

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 paragraph: purpose first, then filter semantics, then return payload. Dense but every clause carries information; the only mild redundancy is describing return fields when an output schema already exists.

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 five-parameter, zero-required, read-only list tool with a full schema and an output schema, the definition covers purpose, filter composition, enum meanings and downstream routing. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further: depth is explained tier by tier ('specified: written in full; derived: restates a chapter 23 seed; stub: outline with open questions') and query clarifies AND-matching across id, title and objective, which the schema only gestures at. The layer parenthetical ('stack layer 1-5, primary or secondary') is slightly confusing against an integer 1-5 schema, which keeps this from a 5.

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?

States a specific verb and resource ('List the reference controls of the open control profiles') and scopes it further to draft specs with stable ids. It also differentiates from the sibling get_control by saying it returns ids for get_control, so an agent knows this is the discovery step, not the detail step.

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?

Explains that all filters are optional and combine with AND, which tells the agent how to compose a query. It also implicitly routes to get_control for full details, but never states when not to use this tool (e.g., when the id is already known, go straight to get_control).

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.