santismm-knowledge

Official

by santismm

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Get an Enterprise AI Pattern

get_pattern

Read-onlyIdempotent

Retrieve a full Enterprise AI pattern by slug after searching or listing patterns, including its problem, solution, KPIs, failure modes, and lessons.

Instructions

Get one Enterprise AI pattern by slug (includes problem, solution, KPIs, failure modes, lessons). Use this once search or list_patterns 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_pattern"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Pattern slug, e.g. 'human-approval-gate'.
`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 a safe, read-only, idempotent operation, so the safety profile is covered. The description adds content context (problem, solution, KPIs, failure modes, lessons), but does not discuss error behavior, locale effects, or other traits beyond annotations.

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 short sentences, front-loaded with the core action and then the usage condition. Every sentence earns its place with no 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?

The tool is simple, the annotations fully cover safety, the schema fully documents both parameters, and an output schema exists. The description provides sufficient context for an agent to know what it returns and when to call it.

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?

With 100% schema description coverage, the schema already documents both `slug` and `locale` including examples, length bounds, enum values, and default. The description adds only the phrase 'by slug', so it does not meaningfully extend parameter meaning beyond the schema.

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: retrieve one Enterprise AI pattern by slug. It also lists the pattern sections returned, making the resource concrete and distinguishable from sibling list/search tools.

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 says to use this after `search` or `list_patterns` has produced a slug. This names the likely alternatives and the triggering condition, leaving little inference needed.

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