Skip to main content
Glama
Creed-Space

creedspace-mcp

Official
by Creed-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_system_prompt

Read-only

Retrieve a complete system prompt for a persona, including constitution and UVC qualities, to enforce AI safety guardrails.

Instructions

Get a complete system prompt for a persona including constitution and UVC qualities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persona_idNoThe persona IDambassador

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
personaIdYesThe persona the prompt was built for
systemPromptYesAssembled system prompt text
creedAttestationYesAttestation line binding the prompt 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": {
+    "creedAttestation": {
+      "description": "Attestation line binding the prompt to the active creed hash",
+      "type": "string"
+    },
+    "personaId": {
+      "description": "The persona the prompt was built for",
+      "type": "string"
+    },
+    "systemPrompt": {
+      "description": "Assembled system prompt text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "personaId",
+    "systemPrompt",
+    "creedAttestation"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, so no side-effect disclosure is needed. The description adds useful context about the content of the returned prompt (includes constitution and UVC qualities), going beyond the annotation.

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 with no unnecessary words. It efficiently conveys the purpose and content of the tool.

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?

For a simple get operation with no output schema, the description provides enough context. It does not mention error cases or how to discover personas, but given the sibling tools (e.g., list_personas), an agent can infer the workflow. The absence of an output schema means no need to document return values.

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 'persona_id' is documented in the schema with a default value. The tool description relates the parameter to 'a persona,' and the schema provides a basic description. This is sufficient for correct usage, though it could benefit from listing valid persona IDs or linking to a listing tool.

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 action ('Get'), the resource ('system prompt for a persona'), and the scope (includes constitution and UVC qualities). It distinguishes itself from sibling tools like get_constitution or get_uvc_qualities by indicating it retrieves the full combined prompt.

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

Usage Guidelines4/5

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

The description implies when to use this tool (when a complete system prompt is needed) but does not explicitly mention alternatives or when not to use it. The meaning is clear enough for an agent to infer, but a direct comparison with siblings would improve guidance.

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