Skip to main content
Glama
Sign In
witness

witness

by wookat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

session_md

Render the evidence timeline for a recorded session as markdown, pairing each spoken SAY block with its attached events so agents can review what happened.

Instructions

The rendered evidence timeline (SAY blocks + attached events)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "session_md"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses only that the output is a rendered timeline containing SAY blocks and attached events, without stating whether the operation is read-only, what scope or size of evidence it covers, or how it relates to live session state.

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 extremely short and contains no wasted wording; every phrase contributes to identifying the returned artifact. Its terseness is efficient, though it is a sentence fragment rather than a structured statement.

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

Completeness3/5

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

For a zero-parameter tool with no annotations and no output schema, the description gives a minimal indication of the return value: a rendered evidence timeline containing SAY blocks and attached events. It is adequate as a bare minimum but leaves important context about format, scope, and intended use unstated.

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?

The tool has zero parameters, so there is no parameter semantics to explain. The baseline of 4 is appropriate because the input schema is trivially complete and the description does not need to add parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the returned artifact as a 'rendered evidence timeline' composed of 'SAY blocks + attached events,' which gives some purpose. However, it is a noun phrase with no verb and does not clearly distinguish its role from siblings such as session_overview, list_says, or segment_detail.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. The description implies it provides a combined rendered timeline, but it neither names sibling tools nor states conditions or exclusions for selecting this tool.

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