Skip to main content
Glama
Creed-Space

creedspace-mcp

Official
by Creed-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_persona

Idempotent

Switch the current session to a different AI persona, selecting from available options to adjust the assistant's behavior and tone.

Instructions

Switch to a different AI persona for the current session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persona_idYesThe persona ID to switch to

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPersona ID
iconYesPersona icon (emoji)
nameYesHuman-readable persona name
messageYesHuman-readable confirmation of the switch
descriptionYesPersona description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "description": {
+      "description": "Persona description",
+      "type": "string"
+    },
+    "icon": {
+      "description": "Persona icon (emoji)",
+      "type": "string"
+    },
+    "id": {
+      "description": "Persona ID",
+      "type": "string"
+    },
+    "message": {
+      "description": "Human-readable confirmation of the switch",
+      "type": "string"
+    },
+    "name": {
+      "description": "Human-readable persona name",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "icon",
+    "description",
+    "message"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, which already convey key behavioral traits. The description adds only that the change applies to the current session, but does not mention potential side effects, permissions, or state persistence beyond that.

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 redundancy or unnecessary detail. It is well-structured and easy to parse.

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?

The description is sufficient for a simple setter operation and provides the scope ('current session'). However, it does not mention error handling, return values, or behavior when an invalid persona_id is provided, which could be helpful in a more complex 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 schema provides a description for persona_id ('The persona ID to switch to') and an enum list, giving 100% coverage. The main description does not add semantic detail beyond what is already in the parameter description, so the added value is minimal.

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 ('Switch'), the resource ('AI persona'), and the scope ('for the current session'). It distinguishes the tool from sibling read-only tools like get_active_persona or list_personas.

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 this tool is for changing the persona rather than querying it, but it does not explicitly state when to use or when not to use it compared to alternatives. The 'different' wording hints at a change operation but lacks explicit 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