Skip to main content
Glama
Creed-Space

creedspace-mcp

Official
by Creed-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_uvc_qualities

Read-only

Retrieve the desired, disliked, and never qualities for a specified persona from the UVC system, using the provided persona ID.

Instructions

Get the desired, disliked, and never qualities for a persona from the UVC system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persona_idNoThe persona IDambassador

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
personaIdYesThe persona the qualities belong to
qualitiesNoValue qualities for the persona; null when UVC is not configured
configuredYesFalse when no UVC qualities are configured for the persona

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "configured": {
+      "description": "False when no UVC qualities are configured for the persona",
+      "type": "boolean"
+    },
+    "personaId": {
+      "description": "The persona the qualities belong to",
+      "type": "string"
+    },
+    "qualities": {
+      "description": "Value qualities for the persona; null when UVC is not configured",
+      "properties": {
+        "desired": {
+          "description": "Desired qualities",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "disliked": {
+          "description": "Disliked qualities",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "never": {
+          "description": "Forbidden qualities",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "personaId",
+    "configured"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds no behavioral details beyond stating it retrieves qualities, such as error handling, default persona behavior, or limits. It is consistent with annotations but provides minimal added transparency.

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 sentence that front-loads the action and resource. It contains no filler and is appropriately sized for a simple getter 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?

Given the tool has only one optional parameter and an output schema (which covers return structure), the description is sufficient for basic invocation. It does not address edge cases or alternative usage, but for a simple read-only getter the descriptions covers the essential 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?

Schema coverage is 100% and the parameter 'persona_id' is already described as 'The persona ID' with a default. The description adds no extra meaning or constraints beyond what the schema provides, so the baseline 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 verb 'Get' and specifies the resource as 'desired, disliked, and never qualities for a persona from the UVC system'. It is specific enough to distinguish from sibling tools like get_constitution or get_system_prompt, which target different resources.

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. It does not mention any context for selection, such as comparing to other getters or explaining that it is the only way to retrieve persona qualities. The agent has to infer usage from the name and schema alone.

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