Skip to main content
Glama
Sign In

InsideOut (Riley)

by com.luthersystems.app
OverviewDiscussionsAdmin

Inspect Session Transcript

convoinspect
Read-only

INSPECTION: View a session's conversation transcript and metadata Returns the full message history (user / assistant / tool turns) plus the session's meta — workflow step, cloud, deployment status, drift state.

This is the transcript-reader companion to the other read tools — combine it with: • convostatus for the live stack / config / pricing • tfruns for deployment history (apply / destroy / plan / drift) • stackversions for the stack-version ladder

Use it when a user asks 'what did I say earlier?' or you need to retrace why the session ended up where it did. Read-only; never mutates session state.

REQUIRES: session_id (format: sess_v2_...).

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>"
    },
    "name": "convoinspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesSession ID from convoopen — pass back EXACTLY as returned, including the ?token=... suffix (format: sess_v2_*?token=*). The suffix is part of the session credential; never strip it when summarizing.

Output Schema

NameRequiredDescriptionDefault
idNoSession ID (without the token suffix).
metaNoSession metadata from the backend (stack, deploy and credential state).
hintsNoGuidance for the calling agent: what to do next and which tools relate to this result.
messagesNoConversation transcript, oldest first. System rows are removed.
createdAtNoSession creation time as a Unix timestamp in milliseconds.
updatedAtNoLast update time as a Unix timestamp in milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "createdAt": {
+      "description": "Session creation time as a Unix timestamp in milliseconds."
+    },
+    "hints": {
+      "description": "Guidance for the calling agent: what to do next and which tools relate to this result.",
+      "properties": {
+        "next_actions": {
+          "description": "Suggested next steps, in order, often as ready-to-run tool calls.",
+          "items": {
+            "description": "One suggested next step.",
+            "type": "string"
+          },
+          "type": [
+            "null",
+            "array"
+          ]
+        },
+        "related_tools": {
+          "description": "Names of tools that are useful after this result.",
+          "items": {
+            "description": "A tool name.",
+            "type": "string"
+          },
+          "type": [
+            "null",
+            "array"
+          ]
+        }
+      },
+      "type": [
+        "null",
+        "object"
+      ]
+    },
+    "id": {
+      "description": "Session ID (without the token suffix).",
+      "type": "string"
+    },
+    "messages": {
+      "description": "Conversation transcript, oldest first. System rows are removed.",
+      "items": {
+        "description": "One message.",
+        "properties": {
+          "content": {
+            "description": "Message text.",
+            "type": "string"
+          },
+          "createdAt": {
+            "description": "Creation time as a Unix timestamp in milliseconds."
+          },
+          "id": {
+            "description": "Message ID.",
+            "type": "string"
+          },
+          "internal": {
+            "description": "Set when the message is internal to the session."
+          },
+          "name": {
+            "description": "Optional author name.",
+            "type": "string"
+          },
+          "role": {
+            "description": "Author role: 'user' or 'assistant'.",
+            "type": "string"
+          }
+        },
+        "type": [
+          "null",
+          "object"
+        ]
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "meta": {
+      "description": "Session metadata from the backend (stack, deploy and credential state).",
+      "type": [
+        "null",
+        "object"
+      ]
+    },
+    "updatedAt": {
+      "description": "Last update time as a Unix timestamp in milliseconds."
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / session_id / description
      Added value: +"Session ID from convoopen — pass back EXACTLY as returned, including the ?token=... suffix (format: sess_v2_*?token=*). The suffix is part of the session credential; never strip it when summarizing."
    • addedInput schema / properties / session_id / pattern
      Added value: +"^sess_v2_[0-9A-Za-z]+\\?token=[0-9a-f]+$"
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description's 'Read-only; never mutates session state' merely restates it. The enumerated return payload (message history plus workflow step, cloud, deployment status, drift state) is largely duplicative of the existing output schema. It does not explain what idempotentHint=false means in practice or disclose any auth/credential nuance beyond what the schema already states.

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 the core capability before the routing bullets, and the bulleted sibling list is compact and earns its place as a disambiguation aid. The trailing 'REQUIRES:' line duplicates the schema and is the one section that could be dropped.

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?

With an output schema present, the description needn't explain return values, and it covers the calling precondition, the read-only guarantee, and sibling routing, so an agent has everything needed to invoke it. The only shortfall is redundancy rather than a genuine gap — it over-explains returns that the output schema already supplies.

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?

Only one parameter, and schema description coverage is 100% — the schema already documents the sess_v2_*?token=* pattern and warns not to strip the token suffix. The description's 'REQUIRES: session_id (format: sess_v2_...)' restates the schema rather than adding new semantic detail, so the baseline 3 applies.

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 (View/Inspect) and resource (a session's conversation transcript and metadata), and explicitly positions itself as the 'transcript-reader companion to the other read tools' while naming convostatus, tfruns, and stackversions as distinct siblings. An agent can distinguish it from the thirteen other read/inspect tools without opening a 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 trigger ('what did I say earlier?', retracing why a session ended up where it did) and routes each alternative use case to a specific sibling with the condition that selects it (convostatus for live stack/config/pricing, tfruns for deployment history, stackversions for version ladders). Nothing 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.

All InsideOut (Riley) toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources