Skip to main content
Glama
Creed-Space

creedspace-mcp

Official
by Creed-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_constitutions

Read-only

Find constitutional AI safety guidelines by searching keyword or persona, enabling targeted content evaluation rules.

Instructions

Search constitutions by keyword or persona

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query
persona_idNoFilter by persona ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoEcho of the search query, when one was supplied
personaYesPersona filter applied, or "all"
resultsYesNumber of matching constitutions
constitutionsYesMatching constitutions (content truncated to a 200-character preview)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "constitutions": {
+      "description": "Matching constitutions (content truncated to a 200-character preview)",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Constitution ID",
+            "type": "string"
+          },
+          "isSystem": {
+            "description": "True for built-in system constitutions",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Constitution name",
+            "type": "string"
+          },
+          "persona": {
+            "description": "Owning persona ID, when persona-scoped",
+            "type": "string"
+          },
+          "preview": {
+            "description": "First 200 characters of the content",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "isSystem",
+          "preview"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "persona": {
+      "description": "Persona filter applied, or \"all\"",
+      "type": "string"
+    },
+    "query": {
+      "description": "Echo of the search query, when one was supplied",
+      "type": "string"
+    },
+    "results": {
+      "description": "Number of matching constitutions",
+      "type": "number"
+    }
+  },
+  "required": [
+    "persona",
+    "results",
+    "constitutions"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorld=true, so the safe, non-destructive nature is covered. The description adds no behavioral detail beyond that, but the annotation coverage is sufficient.

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, compact sentence with no redundancy. It front-loads the action and resource, making it 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?

For a simple search tool, the description is adequate. An output schema exists but is not described; however, the search intent is clear, and no complex side effects or edge cases are relevant.

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?

Both parameters have concise, meaningful descriptions in the schema ('Search query' and 'Filter by persona ID'). Schema coverage is 100%, and the values align with the stated search scope.

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?

Clearly states the verb 'Search' and the resource 'constitutions', with scope 'by keyword or persona'. This distinguishes it from sibling tools like get_constitution which fetches a specific document.

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 use for keyword/persona-based searches but does not explicitly state when to prefer this over alternatives such as get_constitution or list_personas. No explicit when/when-not guidance 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

Other Tools