Skip to main content
Glama

emet_transcript_append

Append one user-assistant exchange to a session transcript after each reply, with idempotent indexing and part rollover to keep conversation records complete and ordered.

Instructions

Append ONE exchange to the session transcript. Call after every reply. Idempotent on exchange_index. Rolls to a new part after 8 exchanges. After a complete close the session takes exactly ONE more append - its closing exchange, numbered next, within EMET_CLOSE_GRACE_MINUTES (default 5) of the close; it is written into the session's last part whatever session_id it names, and the result's closing_exchange says it was accepted and that the session is now locked. A retry of that exchange number is answered as already saved and writes nothing. exchange_index, when given, must be a whole number of 1 or more (a number or its text). Any other append to a closed session is refused and nothing is written; that exchange belongs in the next session you open the usual way. THE FIRST SUCCESSFUL APPEND OF A SESSION IS CHECKED, at whatever exchange_index opens the transcript or becomes the lowest stored index. A refused exchange 1 does not let a higher index start the transcript. Its assistant_message must carry the measured machine line - a machine name from the install notes plus the clock reading, as the shell returned them - or the words no local shell MCP. Without one of those the append is refused and nothing is written.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "user_message": "<user_message>",
      "assistant_message": "<assistant_message>"
    },
    "name": "emet_transcript_append"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoSource tag - which host produced this write. One name on every write since 2026-09-27.
channelNoAlias of `source` (the older name, kept one release). Prefer `source`.
session_idYes
user_messageYes
session_startNo
exchange_indexNo
assistant_messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior1/5

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

The description says the operation is 'Idempotent on exchange_index' and that retries are answered as already saved and write nothing. The annotations declare idempotentHint=false, which directly contradicts that behavioral claim. Although the description otherwise contains rich close, locking, and refusal details, this inconsistency is serious.

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

Conciseness2/5

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

The purpose is front-loaded, but the remainder is a dense wall of run-on procedural rules with capitalization and repetition. Much of the content is relevant, yet the length and formatting make it harder to parse than necessary. It is not concise.

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 a complex mutation tool with no output schema and low schema coverage, the description supplies substantial behavioral context: close grace, locking, retry handling, first-append checking, and machine-line requirements. It still omits detail on several parameters and the general return shape, but the core refusal and lifecycle rules are present.

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 description coverage is only 29%, so the description must carry more of the parameter burden. It does add important meaning for exchange_index, assistant_message, and session_id during close, but it leaves session_start, user_message, source, and channel mostly to the sparse schema. The partial compensation is adequate but incomplete.

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 states a specific verb and resource: append one exchange to the session transcript. It also says to call after every reply, making the immediate purpose clear. It does not explicitly differentiate itself from transcript siblings such as save_transcript or revise_transcript, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit timing guidance ('Call after every reply') and detailed when-not rules for closed sessions. It also explains what to do after a refused append: put the exchange in the next session opened the usual way. The conditions around close grace and exchange numbering are unusually specific.

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