Skip to main content
Glama
Creed-Space

creedspace-mcp

Official
by Creed-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_personas

Read-only

Lists available AI personas with their descriptions and current status. Use to see which personas are ready for content evaluation.

Instructions

List all available AI personas with their descriptions and current status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
currentYesCurrently active persona ID for this session
availableYesAll personas available from the Creed Space API

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "available": {
+      "description": "All personas available from the Creed Space API",
+      "items": {
+        "properties": {
+          "active": {
+            "description": "Whether the persona is active",
+            "type": "boolean"
+          },
+          "description": {
+            "description": "Persona description",
+            "type": "string"
+          },
+          "icon": {
+            "description": "Persona icon (emoji)",
+            "type": "string"
+          },
+          "id": {
+            "description": "Persona ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Human-readable persona name",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "icon",
+          "description",
+          "active"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "current": {
+      "description": "Currently active persona ID for this session",
+      "type": "string"
+    }
+  },
+  "required": [
+    "current",
+    "available"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.3

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, which covers safety and scope. The description adds that results will include descriptions and current status, which is mild value beyond the annotations. It does not discuss pagination, order, or response structure, but for a simple read-only list with annotations this is acceptable.

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?

A single sentence, 'List all available AI personas with their descriptions and current status', with no filler. It front-loads the action and resource, giving the essential information instantly.

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 this is a 0-parameter read-only list with an output schema present, the description is complete: it specifies what is listed and what fields appear. It does not need to explain return values because the output schema already provides that. A minor lack is no mention of pagination/order, but that is not required for a simple listing with an output schema.

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?

There are zero parameters, so the input schema is fully covered at 100% and there are no parameter semantics for the description to clarify. Per the rubric, a tool with no parameters earns a baseline 4; the description exposes the list's content rather than adding parameter behavior.

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 states a specific verb and resource: 'List all available AI personas' with an extra detail on what the listing includes ('descriptions and current status'). It is clearly distinguished from siblings like set_persona (mutating) and get_active_persona (single item) by the 'all available' phrasing.

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?

Usage is implied rather than explicit: 'List all available AI personas' conveys this is for enumeration, and the sibling set shows alternatives like get_active_persona, but the description does not explicitly say when to prefer this over those or include any when-not-to-use 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