creedspace-mcp

Official

Overview Schema Source Related Servers Discussions Admin

preview_export

Preview export configuration for Claude Code or other AI tools to verify persona, UVC qualities, constitutions, and system prompt settings before deployment.

Instructions

Preview the export configuration for Claude Code or other AI tools

Input Schema

TableJSON Schema

Name	Required	Description	Default
`persona_id`	No	The persona ID	ambassador
`include_uvc`	No	Include UVC qualities in export
`include_constitutions`	No	Include constitutions in export
`include_system_prompt`	No	Include system prompt in export

Output Schema

TableJSON Schema

Name	Required	Description
`preview`	Yes	Rendered export preview text
`personaId`	Yes	The persona the export was built for
`includeUvc`	No	Whether UVC qualities were included
`personaName`	Yes	Human-readable persona name
`constitutionIds`	No	Constitution IDs included in the export
`includeSystemPrompt`	No	Whether the system prompt was included
`includeConstitutions`	No	Whether constitutions were included

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.4Sep 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "constitutionIds": {
+      "description": "Constitution IDs included in the export",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "includeConstitutions": {
+      "description": "Whether constitutions were included",
+      "type": "boolean"
+    },
+    "includeSystemPrompt": {
+      "description": "Whether the system prompt was included",
+      "type": "boolean"
+    },
+    "includeUvc": {
+      "description": "Whether UVC qualities were included",
+      "type": "boolean"
+    },
+    "personaId": {
+      "description": "The persona the export was built for",
+      "type": "string"
+    },
+    "personaName": {
+      "description": "Human-readable persona name",
+      "type": "string"
+    },
+    "preview": {
+      "description": "Rendered export preview text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "personaId",
+    "personaName",
+    "preview"
+  ],
+  "type": "object"
+}

First observedv1.1.3Jul 11, 2026

TDQS

C2.7/5.0

Behavior1/5

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

The description says 'Preview', which strongly implies a read-only operation, but the annotation readOnlyHint is false, indicating the tool may have side effects. This is a direct contradiction that could mislead an agent about the tool's safety. No additional behavioral details are provided to clarify what side effects might occur.

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. It is well-structured and free of unnecessary detail, making it easy for an agent to parse quickly.

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?

The description is minimal and lacks information about the expected output format, side effects, or when to prefer this over sibling tools. The read-only contradiction further undermines context, leaving an agent with insufficient guidance for safe and correct usage.

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 schema provides descriptions for all four parameters (persona_id, include_uvc, include_constitutions, include_system_prompt), covering 100% of them. The tool description itself adds no further elaboration on the parameters, so the schema carries the semantic weight. This is adequate but not enhanced by the description.

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 tool previews export configuration for Claude Code or other AI tools, using a specific verb ('Preview') and resource ('export configuration'). It is distinguishable from sibling tools that fetch individual components like constitutions or system prompts, though it does not explicitly name them.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or typical scenarios. An agent would have to infer that previewing is appropriate when planning an export, but no explicit direction is given.

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

Deploy Server