Skip to main content
Glama

List templates and schemas

list_templates
Read-onlyIdempotent

List the templates-and-schemas library: JSON Schemas (with a filled example and a human Markdown template) for the records a governed AI lifecycle produces, from the use-case record to the decommissioning runbook, and the organisation-wide policy kit (AI policy in YAML, prose and Rego, committee charter, RACI, literacy curriculum, contract checklist). Optionally filter by lifecycle stage (intake, build, test, release, operate, retire, organisation). Returns names for get_template.

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

Input Schema

NameRequiredDescriptionDefault
stageNoLifecycle stage id.

Output Schema

NameRequiredDescriptionDefault
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).
templatesYes
dataVersionYesBody of Knowledge version of the data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/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 that results are names only (a payload detail relevant to callers), but says nothing about ordering, pagination, or result size for what could be a large catalog.

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 action and resource, then useful content detail, then the optional filter and the get_template pointer. The parenthetical inventory is dense and somewhat long, but each item materially describes coverage rather than padding.

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?

With an output schema present, the description need not document return fields, and it still notes that names are returned for use with get_template. For a single optional-parameter list tool, an agent has everything needed to call it and follow up correctly.

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 only says 'Lifecycle stage id', so the description adds real value by enumerating the accepted stage values (intake, build, test, release, operate, retire, organisation). That is meaning beyond the schema, though it omits whether an invalid or absent stage is tolerated.

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 templates-and-schemas library') and then enumerates what the library contains — JSON Schemas with filled example and Markdown template, plus the policy kit items. This clearly separates it from get_template, which the description explicitly names as the follow-up for retrieving a specific entry.

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?

Gives the intended use (browse the library), states that stage filtering is optional, and routes the agent to get_template for fetching content. It does not state when NOT to use it or contrast with other list_* siblings, but the get_template handoff gives a clear workflow.

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.