creedspace-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_anchor

Read-only

Retrieve a compact anchor with the top 10 non-negotiable rules and creed hash to reinforce context for AI safety guardrails. Specify persona and max length to get a tailored 1-2KB context snippet.

Instructions

Get a compact anchor (1-2KB) with top 10 non-negotiable rules and creed hash for quick context reinforcement

Input Schema

TableJSON Schema

Name	Required	Description	Default
`max_length`	No	Maximum length of anchor in characters (100-2000)
`persona_id`	No	The persona ID	ambassador

Output Schema

TableJSON Schema

Name	Required	Description
`anchor`	Yes	Compact anchor text
`persona`	Yes	Human-readable persona name
`maxLength`	Yes	Maximum length applied
`personaId`	Yes	The persona the anchor was built for
`truncated`	Yes	True when the anchor was cut to fit max_length
`totalRules`	No	Total rules in the merged creed

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.4Sep 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "anchor": {
+      "description": "Compact anchor text",
+      "type": "string"
+    },
+    "maxLength": {
+      "description": "Maximum length applied",
+      "type": "number"
+    },
+    "persona": {
+      "description": "Human-readable persona name",
+      "type": "string"
+    },
+    "personaId": {
+      "description": "The persona the anchor was built for",
+      "type": "string"
+    },
+    "totalRules": {
+      "description": "Total rules in the merged creed",
+      "type": "number"
+    },
+    "truncated": {
+      "description": "True when the anchor was cut to fit max_length",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "personaId",
+    "persona",
+    "anchor",
+    "truncated",
+    "maxLength"
+  ],
+  "type": "object"
+}

First observedv1.1.3Jul 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate this is a read-only, open-world operation. The description adds non-redundant context by specifying the output compactness (1-2KB), the content (top 10 rules, creed hash, and how this serves quick reinforcement). No contradictions with annotations.

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, tightly-written sentence that front-loads the core action ('Get a compact anchor') and immediately conveys its size and content, with no waste words.

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?

With only 2 optional parameters, comprehensive schema descriptions, an output schema, and annotations covering read-only / open-world, the description completes the main context. It explains the output's purpose but could be slightly more explicit about when to choose it over get_constitution or get_system_prompt.

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 descriptions already exist for max_length and persona_id. The tool description does not need to add parameter-specific meaning; it kept the baseline of 3, meaning no extra value beyond schema is offered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the verb ('Get'), resource ('anchor'), and specific includes (top 10 non-negotiable rules and creed hash). It communicates the compact nature and the purpose, though it does not explicitly compare to sibling tools like get_constitution or get_system_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?

It clearly provides a usage context ('for quick context reinforcement'), which implies when an agent might want this instead of a full document. However, it does not explicit delimit alternatives or state when not to use it, so it does not reach a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server