Skip to main content
Glama
event4u-app

@event4u/agent-config

Official

chat_history_append

Append one structured entry to the chat-history log to record decisions, notes, or phase markers that persist across sessions and can be distilled later.

Instructions

Append one structured entry to the consumer project's chat-history log (a JSONL file). Use to record a decision, note, or phase marker that should persist into a later session or be distilled by mine_session. Writes to the filesystem (agents/runtime/.agent-chat-history by default; agents/.agent-chat-history and .agent-chat-history accepted for back-compat) and returns the written entry plus its resolved target path. Path-scoped: a path outside the allowlist, or any traversal escaping the project root, raises an error before writing. Set dry_run: true to preview the entry and target path without touching disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe entry body to record.
entry_typeNoShort ``t`` tag categorising the entry (e.g. note, decision, phase). Defaults to ``note``.
pathNoOptional path override. Must resolve to `agents/runtime/.agent-chat-history` (current default), `agents/.agent-chat-history`, or `.agent-chat-history` under consumer_root.
sessionNoOptional 16-char session id to group the entry under. Defaults to the current session.
dry_runNoWhen true, return the entry and resolved target path without writing to disk.
min_schema_versionNoRefuse to write if the on-disk history schema is older than this version.
Behavior5/5

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

No annotations, so full burden is on description. Discloses filesystem writes, allowed paths, error on path traversal, dry_run behavior, return of entry and target path. Very transparent.

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?

Concise multi-sentence description starting with primary purpose, then usage, then path details, then dry_run. No fluff, well-structured.

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

Completeness5/5

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

Complete for a tool with 6 params (1 required), no output schema, no annotations. Covers filesystem interaction, error handling, dry run, compatibility, and relation to mine_session.

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 has 100% coverage with descriptions. Description adds context beyond schema: explains entry structure, session grouping, path scoping behavior, dry_run preview. Adds significant value.

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 verb 'append' and resource 'chat-history log (a JSONL file)'. Differentiates from siblings like chat_history_read and mine_session by focusing on writing entries.

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 states use cases: record decision, note, or phase marker for persistence or distillation. Mentions dry_run for preview. Could improve by explicitly stating when not to use, but context is clear.

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/event4u-app/agent-config'

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