Skip to main content
Glama
protosskai

chatgpt-context-mcp

by protosskai

Get Cached ChatGPT Context

get_chatgpt_context

Retrieve a cached ChatGPT conversation by its ID. Supports output in markdown, messages, or JSON format with an optional character limit.

Instructions

Read an already imported ChatGPT conversation from local cache. This does not check the remote conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversation_idYes
formatNo
max_charsNo
Behavior3/5

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

The description indicates a read-only operation from local cache with no side effects, which is adequate. But it does not disclose behavior on missing conversation IDs, error conditions, or any potential hazards, leaving some uncertainty.

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 extremely concise, consisting of two short sentences that convey the core purpose and a key constraint, with no redundant information.

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

Completeness2/5

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

Given the absence of an output schema and the presence of three parameters, the description is too brief. It fails to describe return values, the effect of the format parameter, or how max_chars interacts with the output, leaving significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds no information about the three parameters (conversation_id, format, max_chars). The agent must infer their meaning only from the schema's property names and types, which is insufficient.

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?

The description clearly states the verb 'Read' and the resource 'an already imported ChatGPT conversation from local cache', distinguishing it from siblings that may involve remote operations.

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 specifies that the tool reads from local cache and does not check remote, implying it should be used when the conversation is already imported. However, it does not explicitly state when not to use it or name alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/protosskai/chatgpt-context-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server