Skip to main content
Glama
Creed-Space

creedspace-mcp

Official
by Creed-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_constitution

Read-only

Retrieves the merged constitution for a specified persona, combining active rules and UVC qualities.

Instructions

Get the merged constitution for a specific persona, including all active rules and UVC qualities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persona_idNoThe persona ID (e.g., "ambassador", "nanny", "sentinel")ambassador

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconNoPersona icon (emoji)
contentYesMerged constitution text
personaYesHuman-readable persona name
uvcTokenNoUVC token, when configured for the persona
totalRulesYesTotal number of rules in the merged creed
creedAttestationNoAttestation line binding this response to the active creed hash

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": "Merged constitution text",
+      "type": "string"
+    },
+    "creedAttestation": {
+      "description": "Attestation line binding this response to the active creed hash",
+      "type": "string"
+    },
+    "icon": {
+      "description": "Persona icon (emoji)",
+      "type": "string"
+    },
+    "persona": {
+      "description": "Human-readable persona name",
+      "type": "string"
+    },
+    "totalRules": {
+      "description": "Total number of rules in the merged creed",
+      "type": "number"
+    },
+    "uvcToken": {
+      "description": "UVC token, when configured for the persona",
+      "type": "string"
+    }
+  },
+  "required": [
+    "persona",
+    "totalRules",
+    "content"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.3

TDQS

A4/5.0
Behavior4/5

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

The read-only nature is already indicated by the readOnlyHint annotation, so no additional side-effect disclosure is needed. The description adds transparency about the returned content (all active rules and UVC qualities), which helps set expectations.

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 conveys the essential purpose without redundancy. It is well-structured and directly states the tool's function and content scope.

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?

Given the tool's simplicity and the presence of an output schema (not detailed here), the description does not need to explain return values. It sufficiently covers the input and purpose, though it does not mention potential errors or edge cases, which is minor given the context.

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?

The single parameter persona_id is fully described in the schema (including default and examples), achieving 100% coverage. The tool description does not add supplementary meaning beyond the schema, so the baseline score of 3 applies.

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 the tool retrieves a merged constitution for a specific persona, including active rules and UVC qualities. It uses a specific verb ('Get') and identifies the resource ('merged constitution') and scope ('for a specific persona'), effectively distinguishing it from tools like get_constitution_by_id.

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?

The description implies usage via 'for a specific persona' and the persona_id parameter, but does not explicitly contrast with alternatives such as get_constitution_by_id or list_personas. No explicit guidance on when to prefer this tool over others is provided.

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