Skip to main content
Glama
dreamforgestudiollc

EMET

by dreamforgestudiollc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

save_transcript

FALLBACK. The primary path is emet_session_open then emet_transcript_append after every reply; use this only where a host cannot append per reply. Saves the full word-for-word dialog of a session - full transcripts only, no summaries.

Instructions

FALLBACK. The primary path is emet_session_open then emet_transcript_append after every reply; use this only where a host cannot append per reply. Saves the full word-for-word dialog of a session - full transcripts only, no summaries. Pass exchanges in the call. The server does not read a file. Refused for a session that was closed complete.

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`.
exchangeNoThe exchange (turn) this write belongs to, counting from 1. A write for exchange n while exchange n-1 was never appended is refused by the session graph until n-1 is appended.
exchangesYesClaude.ai Project mode: full array of exchange objects for this session
session_idYesUnique session identifier, e.g. 'claude_project_2026-05-23_001'
session_endNoUnix timestamp — session end (optional, defaults to now)
session_startYesUnix timestamp — session start

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.5
    • removedInput schema / properties / jsonl_path
      Removed value: -{
-  "description": "CLI mode: absolute path to Claude Code session JSONL file. Tool reads and parses it automatically.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "session_id",
-  "session_start"
-]New value: +[
+  "session_id",
+  "session_start",
+  "exchanges"
+]
  2. Changed1 schema field changedv0.2.2
    • changedInput schema / properties / exchange / description
      Previous value: -"The exchange (turn) this write belongs to, counting from 1. A write for exchange n while exchange n-1 was never appended is flagged by the session graph."New value: +"The exchange (turn) this write belongs to, counting from 1. A write for exchange n while exchange n-1 was never appended is refused by the session graph until n-1 is appended."
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the safety profile (non-read-only, non-destructive, non-idempotent), so the description carries real extra weight: it discloses that exchanges must be passed inline, that the server does not read a file, and that the call is refused for a session already closed complete. It does not address duplicate-write behavior despite idempotentHint=false, which is the one remaining gap.

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?

Front-loads 'FALLBACK.' so the routing decision is the first thing read, and every clause carries a distinct constraint (primary path, per-reply alternative, inline payload, no file read, refusal condition). The dense second sentence is slightly packed but nothing is wasteful.

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 non-idempotent write with no output schema, the description covers the key operational facts: inline data, no server-side file read, whole-transcript requirement, and the closed-complete refusal. Only success/response behavior and duplicate-write handling are unstated.

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 100%, including ordering rules for exchange and naming/aliasing notes for source vs channel, so the schema does the heavy lifting. The description only adds the generic 'pass exchanges in the call' instruction, which is the baseline 3 for a fully documented 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?

States a specific verb+resource (saves a full word-for-word session transcript) and explicitly positions itself as the fallback against named siblings emet_session_open and emet_transcript_append. An agent can distinguish it from the primary append path without opening any schema.

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?

Gives an explicit when-to-use condition ('use this only where a host cannot append per reply') plus the preferred alternative path, and adds an exclusion ('full transcripts only, no summaries'). Nothing about selection is left to inference.

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