Skip to main content
Glama

Get a pattern

get_pattern
Read-onlyIdempotent

Get one governance pattern by slug ("policy-card", "kill-switch-circuit-breaker"), chapter 05 id ("pattern-aibom"), page URL or title: its layer, summary, the frameworks it maps to, the obligation ids that list it and the full text of its page (objectives, context, problem, solution, consequences, related patterns, sources).

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": {
      "slug": "<slug>"
    },
    "name": "get_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPattern slug, id, URL or title.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesCanonical page of the pattern.
slugYes
layerYes
titleYes
mapsToYes
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).
summaryYes
sectionsYesSections of the pattern page, in order (empty when the page text is unavailable).
layerNameYes
dataVersionYesBody of Knowledge version of the data.
obligationsYes
catalogueUrlYesThe pattern in the chapter 05 catalogue.
secondaryLayerYes
obligationDetailsYes
secondaryLayerNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: it accepts several loose identifier formats (slug, chapter id, URL, title) and returns the full page text, which matters for context/token budgeting. It does not say what happens on an unmatched identifier or how title matching behaves.

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?

Front-loaded with the verb, resource and identifier forms, which is the right ordering. The trailing parenthetical enumerating returned sections is long and largely duplicates the output schema, so the sentence is dense and slightly over-stuffed, but nothing is truly wasted.

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?

For a one-parameter, annotation-rich read tool with an output schema, the definition is nearly complete: identifier forms and payload scope are both clear. The remaining gap is error/not-found behavior and the precision of title matching, which an agent would want before calling blindly.

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's slug description already says 'Pattern slug, id, URL or title', so the baseline would be 3. The description earns above baseline by giving concrete examples of the domain-specific formats ('policy-card', 'kill-switch-circuit-breaker', 'pattern-aibom'), which materially clarify what values to pass.

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 (get) and resource (one governance pattern), scoped to a single record ('one'), and contrasts implicitly with the plural list_patterns sibling. It also enumerates the accepted identifier forms, so an agent knows exactly what this tool resolves.

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 implied rather than stated: the agent can infer this is the single-record lookup counterpart to list_patterns, but no explicit when-to-use or when-not-to-use guidance is given and no alternative (e.g. search_bok, list_patterns) is named for the case where the identifier is unknown.

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.