Skip to main content
Glama
aidesignblueprint

AI Design Blueprint Doctrine

Official
by aidesignblueprint
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

principles.get

Read-onlyIdempotent

Retrieve a single doctrine entry (principle, design law, or spec law) by its stable slug. Specify a lens to select the doctrine: architecture, surface, or spec.

Instructions

Get one doctrine entry by stable slug. The lens selects the doctrine: 'architecture' = one of the 10 agentic principles (default); 'surface' = one of the 8 experience-design laws; 'spec' = one of the 8 spec-quality laws. Returns id, title, cluster, definition, rationale, implications, and risk-if-violated (laws also carry their eponym and validator_questions). Use this when you already have the exact slug from principles.list; prefer principles.search when the user describes a topic or failure mode in natural language; prefer principles.list when you need every entry or every entry within a cluster. Returns error_payload on unknown slug for the lens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lensNoWhich public doctrine the slug belongs to: 'architecture' (10 principles, default), 'surface' (8 design laws), or 'spec' (8 spec laws).architecture
slugYesStable slug of the principle (e.g. 'establish-trust-through-inspectability').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / lens
      Added value: +{
+  "default": "architecture",
+  "description": "Which public doctrine the slug belongs to: 'architecture' (10 principles, default), 'surface' (8 design laws), or 'spec' (8 spec laws).",
+  "enum": [
+    "architecture",
+    "surface",
+    "spec"
+  ],
+  "title": "Lens",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_principleDictOutput",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Stable slug of the principle (e.g. 'establish-a-delegation-boundary')."New value: +"Stable slug of the principle (e.g. 'establish-trust-through-inspectability')."
  3. Changed1 schema field changedv1.1.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "get_principleDictOutput",
-  "type": "object"
-}New value: +null
  4. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds that it returns error_payload on unknown slug, and explains the conditional fields per lens. This is useful context 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?

Three sentences, front-loaded core purpose, no wasted words. Each sentence earns its place: purpose, parameter usage, and usage alternatives.

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?

Given the presence of an output schema (inferred), the description adequately lists returned fields and error handling. It covers all necessary context for an agent to correctly select and invoke the tool.

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%, so baseline is 3. Description adds meaning by explaining the lens selects which doctrine, gives example values, and notes that slug comes from principles.list. It also clarifies that return fields differ by lens.

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?

The description clearly states 'Get one doctrine entry by stable slug' and specifies the resource (doctrine entry) and verb (get). It differentiates from siblings by explaining when to use principles.search or principles.list instead.

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 provides when to use this tool ('when you already have the exact slug from principles.list') and when to prefer alternatives ('prefer principles.search when the user describes a topic...'). Also mentions default lens and error behavior.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aidesignblueprint/integrations'

If you have feedback or need assistance with the MCP directory API, please join our Discord server