Skip to main content
Glama
S2thend

cursor-history-mcp

by S2thend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cursor_history_show

Retrieve a Cursor session's messages and tool activity with source and timestamp provenance, filtering by session ID or index.

Instructions

Inspect the available messages and tool activity in a Cursor session, with source and timestamp provenance. Long thinking and tool payloads are abbreviated; use export for unabridged available content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdNoExact native session UUID returned by list/search. Case-sensitive; do not normalize.
workspaceNoWorkspace path. Reuse the same scope for listing and reading a session index.
sessionIndexNoOne-based index from a list with the same workspace scope. Prefer sessionId for reuse.
includeCrossWorkspaceSourcesNoOpt in to complementary sources outside this workspace, only for already selected session IDs. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.1
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "sessionId"
+      ]
+    },
+    "required": [
+      "sessionIndex"
+    ]
+  },
+  {
+    "not": {
+      "required": [
+        "sessionIndex"
+      ]
+    },
+    "required": [
+      "sessionId"
+    ]
+  }
+]
    • addedInput schema / properties / includeCrossWorkspaceSources
      Added value: +{
+  "default": false,
+  "description": "Opt in to complementary sources outside this workspace, only for already selected session IDs. Default: false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / sessionId
      Added value: +{
+  "description": "Exact native session UUID returned by list/search. Case-sensitive; do not normalize.",
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / sessionIndex / description
      Previous value: -"The session index (1-based, as shown in list output)"New value: +"One-based index from a list with the same workspace scope. Prefer sessionId for reuse."
    • addedInput schema / properties / workspace
      Added value: +{
+  "description": "Workspace path. Reuse the same scope for listing and reading a session index.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "sessionIndex"
-]
  2. First observedv0.2.4

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full transparency burden. It usefully discloses that content is read-only ('Inspect'), includes provenance, and that long thinking and tool payloads are abbreviated. It does not cover permissions, side effects, or error behavior, but the core behavioral traits are disclosed.

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

Conciseness5/5

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

The description is two sentences, with the primary purpose first and the key limitation/alternative second. There is no fluff, and each sentence contributes real information.

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?

Given there are no annotations and no output schema, the description still conveys the main output characteristics (messages, tool activity, source, timestamps) and the notable abbreviation behavior. It does not fully specify output format or edge cases, but schema already handles the parameter side, so this is reasonably complete.

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?

Input schema coverage is 100%, and each parameter already has a descriptive meaning. The description itself adds no parameter-level semantics beyond what the schema states, so it lands at the baseline score.

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 clearly states a specific action ('Inspect') and resource ('messages and tool activity in a Cursor session'), with source and timestamp provenance. However, it does not explicitly differentiate it from sibling tools such as cursor_history_list or cursor_history_search, so sibling differentiation is partial.

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?

The description provides a clear alternative: 'use export for unabridged available content.' This directly tells when not to use this tool (when full, unabridged content is needed), but it lacks any guidance on choosing between show, list, and search, leaving usage guidance incomplete.

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