Skip to main content
Glama

a4sx sessions

by com.session-exchange
OverviewDiscussionsAdmin

Save session to library

publish_session

Save a session transcript (JSONL), or markdown you composed (format=markdown), to your private a4sx library. The server only rewrites text that matches secret and personal-data patterns (such as tokens, private keys, emails, IP addresses and home-directory user names). It removes no record or field: a raw Claude Code transcript keeps the user's CLAUDE.md and session context (attachment records), file-history snapshot records (absolute file paths), other non-conversation records (such as pr-link), tool-output copies (toolUseResult), and cwd, gitBranch and version on every line; the reply counts them (except version) in unprepared_carriers. Prepare the transcript or compose markdown first, as GET /orient on this server without auth describes (route A, or route B steps 0-8). Private: it is never listed publicly by this tool.

Input Schema

NameRequiredDescriptionDefault
labelNo
titleNo
formatNojsonl: a transcript. markdown: content you composed (route A in GET /orient on this server without auth); stored as sent, after the same server scrub.jsonl
parentNoLibrary id this session continues from (lineage).
transcriptYesThe session transcript as JSONL (Claude Code or Codex CLI format; detected automatically), or markdown you composed with format=markdown.
visibilityNoAlways private. Listing publicly is a separate step in the web app.private
content_sha256NoHex SHA-256 of the transcript's UTF-8 bytes; checked.
client_scrubbedNoThe client scrubbed before sending. The server scrubs again regardless.
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
+  "default": "jsonl",
+  "description": "jsonl: a transcript. markdown: content you composed (route A in GET /orient on this server without auth); stored as sent, after the same server scrub.",
+  "enum": [
+    "jsonl",
+    "markdown"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / transcript / description
      Previous value: -"The session transcript as JSONL (Claude Code or Codex CLI format; detected automatically)."New value: +"The session transcript as JSONL (Claude Code or Codex CLI format; detected automatically), or markdown you composed with format=markdown."
  2. Changed1 schema field changed
    • changedInput schema / properties / transcript / description
      Previous value: -"The session transcript as JSONL (Claude Code format)."New value: +"The session transcript as JSONL (Claude Code or Codex CLI format; detected automatically)."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: the server only rewrites text matching secret and personal-data patterns, removes no record or field, preserves raw transcript carriers, and counts them in unprepared_carriers. It also clarifies that the saved session remains private and is not publicly listed by this tool, which is exactly the kind of context an agent needs.

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 purpose is front-loaded in the first sentence, and most of the detail is behaviorally relevant rather than redundant. However, the middle sentence is very dense and references external GET /orient route steps, making the description longer and harder to scan than necessary.

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 save operation with no output schema, the description covers the essential behavior: preparation steps, scrubbing scope, non-removal of records, and privacy. It still leaves some gaps around the full response shape and several individual parameters, but it is largely complete for correct invocation.

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 67%, so the schema already documents several parameters. The description adds useful meaning around transcript format, markdown composition, and private visibility, but it does not explain label, title, parent, content_sha256, client_scrubbed, or idempotency_key beyond what the schema provides.

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: saving a session transcript or composed markdown to a private a4sx library. It is clear what the tool does and how format=markdown differs, but it does not explicitly distinguish itself from sibling tools such as search_sessions or fetch_session_context.

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?

It gives a clear usage context and prerequisite: prepare the transcript or compose markdown first according to GET /orient route A or route B steps 0-8. It does not state explicit when-not-to-use conditions or name alternatives, so it falls short of full routing guidance.

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

All a4sx sessions toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources