Skip to main content
Glama

Get a template or schema

get_template
Read-onlyIdempotent

Get one entry of the templates-and-schemas library by name ("policy-card", "impact-assessment", "incident-record", "ai-policy", "raci"), file name or URL: what it records, its lifecycle stage and stack layers, the clauses it helps evidence, and the content of its files. part picks what to return: "schema" (the JSON Schema), "example" (a filled example that validates against it), "template" (the human Markdown template, or the kit files) or "all" (default).

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

Input Schema

NameRequiredDescriptionDefault
nameYesTemplate name, file name or URL.
partNoWhich files to return.all

Output Schema

NameRequiredDescriptionDefault
kindYesschema: JSON Schema with example and template; kit: policy-kit files.
nameYes
filesYes
stageYes
titleYes
layersYes
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
evidencesYesClauses the record helps evidence (illustrative mapping).
stageLabelYes
dataVersionYesBody of Knowledge version of the data.
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 fully covered structurally. The description's genuinely additive content is the disclosure of what a returned entry contains (metadata plus file bodies), which goes beyond the annotations — but it says nothing about miss behavior when the name isn't found or whether name matching is exact.

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 purpose then parameter semantics, with no filler. The first sentence is dense with comma-separated payload details, but each clause carries distinct information about what comes back.

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 a rich output schema and full annotation coverage, the description only needs to carry input semantics and payload composition, which it does thoroughly. The remaining omission is failure/not-found behavior, which is minor for a read-only lookup but not nothing.

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

Parameters5/5

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

Schema coverage is 100%, so baseline would be 3, but the description meaningfully exceeds the schema: it enumerates concrete valid values for `name` ("policy-card", "impact-assessment", "incident-record", "ai-policy", "raci") and defines what each `part` enum value actually returns — JSON Schema, a validating filled example, the human Markdown template or kit files, and all-as-default. The schema only lists the enum strings; the description explains them.

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?

The description names a specific verb and resource ("Get one entry of the templates-and-schemas library") and enumerates what that entry contains: recorded data, lifecycle stage, stack layers, evidenced clauses, and file contents. This is far clearer than the sibling 'get_*' tools, though it never explicitly contrasts itself with list_templates or search_bok, so the agent must infer the browse-vs-fetch split.

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: "by name, file name or URL" signals that the caller must already know an identifier, and the parenthetical list of five example names gives concrete valid inputs. There is no explicit when-to-use, no when-not-to-use, and no routing to list_templates for callers who don't yet have a name.

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.