Skip to main content
Glama
Sign In
Engram

Engram

by staticroostermedia-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

mcp_engram_genesis

Verify or repair core alignment genesis blocks. Use 'status' to check ethical/operational anchors, or 'reseed' to re-initialize missing or corrupted blocks.

Instructions

BEHAVIOR: Inspects or re-initializes the core alignment genesis blocks of the OS. These are foundational PRAXIS-tagged memories locked at CRS=1.0. USAGE: Call this to verify the ethical/operational anchors exist ('status' action) or to repair the manifold if they are missing/corrupted ('reseed' action). OUTPUT: Text indicating the presence of genesis seeds or confirmation of their successful re-initialization.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcp_engram_genesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNo'status' — show which genesis blocks exist. 'reseed' — re-seed all blocks.status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations provided. Describes reseeding as 'repair' but does not disclose potential data loss or mutation side effects. Incomplete transparency for a re-initialization operation.

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?

Two front-loaded sentences with 'BEHAVIOR' and 'USAGE' labels. Concise, but structure could be improved with clearer separation of actions. No unnecessary 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?

For one-parameter tool with no output schema, description covers purpose, actions, and usage. Lacks details on output format but sufficient for selection and invocation.

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?

Schema covers 100% with enum descriptions. Description adds context: status for 'verify ethical/operational anchors', reseed for 'repair the manifold'. Adds meaning beyond schema.

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 'Inspects or re-initializes' with specific resource 'core alignment genesis blocks'. Uniquely identifies foundational PRAXIS-tagged memories, differentiating it from sibling tools.

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?

Explicitly tells when to use 'status' (verify anchors exist) and 'reseed' (repair missing/corrupted). Lacks explicit non-usage scenarios, but actions are well-defined.

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