Skip to main content
Glama
Creed-Space

creedspace-mcp

Official
by Creed-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_constitution_by_id

Read-only

Fetch a constitution document by its ID to review AI safety guidelines.

Instructions

Get a specific constitution by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
constitution_idYesThe constitution ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesConstitution ID
nameYesConstitution name
contentYesFull constitution text
personaIdNoOwning persona ID, when persona-scoped
uvcQualitiesNoValue qualities for the persona; null when UVC is not configured
isSystemConstitutionYesTrue for built-in system constitutions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "description": "Full constitution text",
+      "type": "string"
+    },
+    "id": {
+      "description": "Constitution ID",
+      "type": "string"
+    },
+    "isSystemConstitution": {
+      "description": "True for built-in system constitutions",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "Constitution name",
+      "type": "string"
+    },
+    "personaId": {
+      "description": "Owning persona ID, when persona-scoped",
+      "type": "string"
+    },
+    "uvcQualities": {
+      "description": "Value qualities for the persona; null when UVC is not configured",
+      "properties": {
+        "desired": {
+          "description": "Desired qualities",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "disliked": {
+          "description": "Disliked qualities",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "never": {
+          "description": "Forbidden qualities",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "content",
+    "isSystemConstitution"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.3

TDQS

A3.5/5.0
Behavior4/5

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

The readOnlyHint annotation already indicates this is a read-only operation, and the description aligns with that by using the verb 'Get'. No side effects are mentioned, and there is no contradiction between the description and 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?

The description is a single, concise sentence that directly states the tool's purpose without unnecessary elaboration or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of a sibling tool 'get_constitution', the description does not clarify the difference, leaving the agent uncertain about which tool to invoke. Additionally, there is no output schema or description of the return value, which could be important for usage.

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?

The single parameter 'constitution_id' is clearly described as 'The constitution ID', which matches the schema. The description fully covers the parameter's meaning, though it adds minimal extra context beyond the name.

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 clearly states the action (get) and resource (a specific constitution by ID). However, it does not differentiate from the sibling tool 'get_constitution', which likely has a similar purpose, creating ambiguity about the exact distinction.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus the sibling 'get_constitution'. The description implies it is for fetching a constitution by ID, but does not explicitly state the alternative or the conditions for choosing this tool over another.

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

Deploy Server

Other Tools