Skip to main content
Glama
Creed-Space

creedspace-mcp

Official
by Creed-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

heartbeat

Read-only

Sends a periodic mini-anchor every 10 messages to prevent context drift and maintain conversational continuity.

Instructions

Periodic re-anchoring to prevent context drift - returns mini-anchor every 10 messages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoForce anchor return regardless of message count
persona_idNoThe persona IDambassador
message_countNoCurrent message count in the session

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesMini-anchor text, or the heartbeat acknowledgement
personaNoHuman-readable persona name; present only when anchored
anchoredYesTrue when a mini-anchor was returned rather than a plain acknowledgement
personaIdYesThe persona used for re-anchoring
messageCountYesMessage count supplied by the caller

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "anchored": {
+      "description": "True when a mini-anchor was returned rather than a plain acknowledgement",
+      "type": "boolean"
+    },
+    "messageCount": {
+      "description": "Message count supplied by the caller",
+      "type": "number"
+    },
+    "persona": {
+      "description": "Human-readable persona name; present only when anchored",
+      "type": "string"
+    },
+    "personaId": {
+      "description": "The persona used for re-anchoring",
+      "type": "string"
+    },
+    "text": {
+      "description": "Mini-anchor text, or the heartbeat acknowledgement",
+      "type": "string"
+    }
+  },
+  "required": [
+    "anchored",
+    "messageCount",
+    "personaId",
+    "text"
+  ],
+  "type": "object"
+}
  2. First observedv1.1.3

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the agent already knows this is a safe, read-only operation. The description adds that it returns a mini-anchor and the frequency, which is useful context. However, it does not disclose any further behavioral details like dependencies on session state or how force modifies behavior. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and front-loaded with the primary purpose. It is easy to scan and contains no filler. However, it is slightly too brief to capture all necessary usage nuances, but for conciseness it is effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 3 optional parameters and an output schema. The description does not clarify when to use force, how message_count interacts with the 'every 10 messages' rule, or how this tool relates to get_anchor. It lacks guidance on prerequisites or conditions for invocation. Given the complexity (multiple params and siblings), the description is incomplete for an agent to decide when to call it correctly.

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% with each parameter having a description, so the baseline for high coverage is 3. The description adds minimal value beyond the schema: it mentions 'every 10 messages' which relates to message_count, but does not explain the purpose of force or persona_id. It does not compensate or enrich the parameter meanings beyond what the schema already provides.

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 clearly states that the tool performs periodic re-anchoring to prevent context drift and returns a mini-anchor every 10 messages. It has a specific verb and resource, and the frequency is mentioned. However, it does not explicitly differentiate from siblings like get_anchor, which might also provide anchors, so it is not fully distinct.

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 implies periodic usage ('every 10 messages') but does not explicitly state when to use this tool versus alternatives such as get_anchor. It does not connect the message_count parameter to the condition, nor does it explain when to use the force parameter. No exclusions or alternative scenarios are provided.

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