santismm-knowledge

Official

by santismm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get an AI Governance Unit

get_governance

Read-onlyIdempotent

Retrieve a complete AI governance unit by slug—including scope, key requirements, implementable controls, checklist, and common pitfalls—after finding the slug via search or listing.

Instructions

Get one AI governance unit by slug (includes scope, key requirements, implementable controls, a checklist and common pitfalls). Use this once search or list_governance has given you a slug.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	Governance unit slug, e.g. 'eu-ai-act'.
`locale`	No	Language of the returned body. Default: en.

Output Schema

Name	Required	Description
`id`	No
`body`	No
`name`	No
`slug`	Yes
`tags`	No
`domain`	Yes
`locale`	No
`status`	No
`aliases`	No
`api_url`	Yes
`locales`	No
`related`	Yes
`summary`	No
`updated`	Yes
`version`	Yes
`category`	Yes
`evidence`	Yes	Evidence-First provenance: weight claims by this.
`fallback`	No
`featured`	No
`patterns`	No
`knowledge`	No
`frameworks`	No
`references`	Yes
`how_to_cite`	No	The citation, already formed — use it verbatim.
`resource_uri`	No
`technologies`	No
`canonical_url`	Yes
`resolved_locale`	No
`requested_locale`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Nov 6, 2026

changedInput schema / properties / locale / enum

Previous value: -[
-  "en",
-  "es",
-  "pt"
-]New value: +[
+  "en",
+  "es",
+  "pt",
+  "fr",
+  "de",
+  "ja",
+  "zh"
+]

addedOutput schema / properties / how_to_cite

Added value: +{
+  "description": "The citation, already formed — use it verbatim.",
+  "type": "string"
+}

Changed6 schema fields changedv0.4.1Sep 2, 2026

addedInput schema / properties / slug / maxLength
```
Added value: +128
```
addedInput schema / properties / slug / minLength
```
Added value: +1
```
changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```

addedOutput schema / properties / aliases

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / resource_uri
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / required

Added value: +[
+  "domain",
+  "slug",
+  "category",
+  "updated",
+  "version",
+  "evidence",
+  "canonical_url",
+  "api_url",
+  "references",
+  "related"
+]

First observedv0.2.1Aug 2, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and repeat-call profile is fully covered without the description. The description adds a preview of the returned content, but since a structured output schema exists this is largely redundant; it says nothing about error behavior for unknown slugs or any auth/rate considerations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler. The purpose and payload preview come first, then the prerequisite, so the most decision-relevant information is front-loaded.

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 single-resource fetch with strong annotations, a 100%-covered schema, and an existing output schema, the description supplies everything an agent needs: what it fetches, what it returns, and when to reach for it. No material gap remains.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters (slug, locale enum) are documented in the schema with an example and default. The description only restates 'by slug' and omits the locale parameter entirely, so it adds no meaning beyond the schema — the baseline 3 for fully covered params is correct.

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+resource ('Get one AI governance unit by slug') and even previews the payload's content (scope, requirements, controls, checklist, pitfalls). This clearly separates it from list_governance (plural, listing) and search, so an agent can pick it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly sequences the workflow: 'Use this once search or list_governance has given you a slug.' This names the alternative tools and the condition under which this one is the right call, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.