Skip to main content
Glama

List patterns

list_patterns
Read-onlyIdempotent

List the reusable governance patterns of the Body of Knowledge (chapter 05), optionally only those of one stack layer (1 Govern-as-Code, 2 Inventory & Transparency, 3 Evals & Red Teaming as Evidence, 4 Runtime Controls & Observability, 5 Assurance & Continuous Compliance; a pattern with a secondary layer is listed under both). Returns slugs for get_pattern, summaries, the frameworks each pattern maps to and the obligation ids that list it.

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

Input Schema

NameRequiredDescriptionDefault
layerNoStack layer, 1 to 5.

Output Schema

NameRequiredDescriptionDefault
layerYes
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.
licenseYesLicence of the data (CC BY 4.0, attribution required).
patternsYes
layerNameYes
dataVersionYesBody of Knowledge version of the data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is carried. The description adds genuine non-obvious behavior: the filter is optional, and a pattern with a secondary layer appears under both layers, which an agent must know to avoid double-counting results.

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 scope, then the return contents. The inline layer enumeration makes the first sentence long and list-heavy, but each element carries operational meaning, so little could be cut without losing filtering guidance.

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 only one optional parameter and a full output schema, this definition covers everything needed to call it correctly: scope, filter semantics, duplication behavior, and downstream use. The return-value sentence partly duplicates the output schema, which is mildly redundant but not harmful.

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% and the schema only says 'Stack layer, 1 to 5', so the description's enumeration of what layers 1 through 5 actually mean is real added meaning rather than repetition. It also confirms the parameter is optional, which the schema supports but does not highlight.

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 reusable governance patterns of the Body of Knowledge (chapter 05)') with precise scope, and the slug/summary return note makes clear it is a discovery tool distinct from get_pattern, which fetches one pattern by slug.

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?

The 'Returns slugs for get_pattern' clause gives clear context for the list-then-fetch workflow, and the optional layer filter defines a concrete narrowing condition. It stops short of stating exclusions (e.g. when to use search_bok instead for keyword lookup), so it is strong but not fully explicit about alternatives.

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.