Skip to main content
Glama

coc_add

Add a tamper-evident entry to a Chain of Consciousness chain, cryptographically linking each event to the previous via SHA-256 hashing for an append-only audit trail.

Instructions

Add an entry to an existing Chain of Consciousness chain.

Each entry is cryptographically linked to the previous via SHA-256 hashing,
creating a tamper-evident append-only log.

Args:
    event_type: Type of event. One of: learn, decide, create, error, note,
                milestone, session_start, session_end, boot, rotate, anchor,
                compaction, governance
    data: Description of what happened (free-form text)
    agent: Name/ID of the agent adding this entry (default: anonymous)
    commitment: For session_end only — SHA-256 hash of expected bootstrap state
                for the next session (forward commitment)
    verification: For session_start only — SHA-256 hash of actual bootstrap state
                  to verify against previous session's commitment

Returns:
    JSON with the new entry details (sequence number, hash, timestamp)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_typeYes
dataYes
agentNoanonymous
commitmentNo
verificationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses key behaviors: entries are cryptographically linked via SHA-256, creating a tamper-evident append-only log. It also explains special parameters for session management. However, it does not mention authentication or rate limits.

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 well-structured with Args and Returns sections, front-loads the main purpose, and every sentence adds value. It could be slightly more concise, but remains clear and informative.

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's complexity (5 parameters, cryptographic behavior) and the presence of an output schema, the description covers essential aspects. It lacks mention of prerequisites (e.g., existence of a chain) and error conditions, but is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description thoroughly explains each parameter: event_type lists allowed values, data is free-form text, agent defaults to anonymous, commitment and verification have specific roles for session boundaries. This adds significant meaning beyond the bare 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?

The description clearly states the tool's purpose: 'Add an entry to an existing Chain of Consciousness chain.' It explains the cryptographic linking and distinguishes this tool from siblings like coc_init (initialization) and coc_status (inspection).

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 usage for appending entries to a chain, but does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or conditions that would make it inappropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexfleetcommander/agent-trust-stack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server