Skip to main content
Glama
taylorleese

mcp-toolz

ask_chatgpt

Get ChatGPT's perspective on saved context entries to verify information or obtain alternative insights for decision-making.

Instructions

Ask ChatGPT a question about a context entry, or get a general second opinion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
context_idYesContext ID to ask about
questionNoOptional specific question to ask about the context. If not provided, gets a general second opinion.

Implementation Reference

  • The main handler for the 'ask_chatgpt' tool within the call_tool method. It retrieves the context by ID, instantiates ChatGPTClient, calls get_second_opinion, optionally updates the storage with the response, and returns the formatted response.
    if name == "ask_chatgpt":
        context_id = arguments["context_id"]
        question = arguments.get("question")
        context = self.storage.get_context(context_id)
        if not context:
            return [TextContent(type="text", text=f"Context {context_id} not found")]
    
        try:
            chatgpt_client = ChatGPTClient()
            response = chatgpt_client.get_second_opinion(context, question)
    
            # Only save to database if it's a generic second opinion (no custom question)
            if not question:
                self.storage.update_chatgpt_response(context_id, response)
    
            header = "ChatGPT's Answer:" if question else "ChatGPT's Opinion:"
            return [TextContent(type="text", text=f"{header}\n\n{response}")]
        except ValueError as e:
            return [TextContent(type="text", text=f"Error: {e}")]
  • Registration of the 'ask_chatgpt' tool in the list_tools method, including name, description, and input schema.
    Tool(
        name="ask_chatgpt",
        description="Ask ChatGPT a question about a context entry, or get a general second opinion",
        inputSchema={
            "type": "object",
            "properties": {
                "context_id": {"type": "string", "description": "Context ID to ask about"},
                "question": {
                    "type": "string",
                    "description": (
                        "Optional specific question to ask about the context. If not provided, gets a general second opinion."
                    ),
                },
            },
            "required": ["context_id"],
        },
    ),
  • Core helper method in ChatGPTClient that constructs the appropriate prompt (system and user) based on whether a specific question is provided, calls the OpenAI ChatGPT API, and returns the response.
        def get_second_opinion(self, context: ContextEntry, question: str | None = None) -> str:
            """Get ChatGPT's second opinion on a context, or answer a specific question.
    
            Args:
                context: The context entry to analyze
                question: Optional specific question to ask. If None, provides general second opinion.
            """
            if question:
                # Custom question mode
                system_prompt = """You are a senior software engineering consultant answering questions about code, \
    architecture decisions, and implementation plans.
    
    Provide clear, actionable answers based on the context provided."""
                user_content = self._format_context_for_chatgpt(context, question)
            else:
                # Generic second opinion mode
                system_prompt = """You are a senior software engineering consultant providing second opinions on code, \
    architecture decisions, and implementation plans from Claude Code.
    
    Your role is to:
    - Provide constructive, balanced feedback
    - Highlight both strengths and potential issues
    - Suggest alternatives when appropriate
    - Point out edge cases or security concerns
    - Be concise but thorough
    
    Format your response clearly with sections as needed."""
                user_content = self._format_context_for_chatgpt(context)
    
            response = self.client.chat.completions.create(
                model=self.model,
                messages=[
                    {"role": "system", "content": system_prompt},
                    {"role": "user", "content": user_content},
                ],
            )
    
            return response.choices[0].message.content or ""
  • Helper method that formats the ContextEntry into a markdown-structured prompt suitable for ChatGPT, including title, type, timestamp, tags, content based on type, and the question or default second opinion request.
    def _format_context_for_chatgpt(self, context: ContextEntry, question: str | None = None) -> str:
        """Format a context entry for ChatGPT consumption.
    
        Args:
            context: The context entry to format
            question: Optional specific question to append
        """
        parts = [
            f"# Context from Claude Code: {context.title}",
            f"\n**Type:** {context.type}",
            f"**Timestamp:** {context.timestamp.isoformat()}",
        ]
    
        if context.tags:
            parts.append(f"**Tags:** {', '.join(context.tags)}")
    
        parts.append("\n## Content\n")
    
        # Add specific content based on type
        if context.content.messages:
            parts.append("### Conversation\n")
            for msg in context.content.messages:
                parts.append(msg)
    
        if context.content.code:
            parts.append("### Code\n")
            for file_path, code in context.content.code.items():
                parts.append(f"**File:** `{file_path}`\n```\n{code}\n```\n")
    
        if context.content.suggestions:
            parts.append(f"### Suggestion\n{context.content.suggestions}\n")
    
        if context.content.errors:
            parts.append(f"### Error/Debug Info\n```\n{context.content.errors}\n```\n")
    
        # Add question or default request
        if question:
            parts.append(f"\n---\n**Question:** {question}")
        else:
            parts.append("\n---\nPlease provide a second opinion on the above context from Claude Code.")
    
        return "\n".join(parts)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions what the tool does but doesn't describe important behavioral traits like response format, rate limits, authentication needs, or whether this is a read-only vs. state-changing operation. The description is functional but lacks operational context.

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 perfectly concise with two clear options in a single sentence. Every word earns its place, and the structure is front-loaded with the primary purpose. No wasted words or unnecessary elaboration.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what kind of response to expect, how ChatGPT will be invoked, or any operational constraints. Given the complexity of interacting with an AI model and the lack of structured output documentation, more context is needed.

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 100%, so the schema already fully documents both parameters. The description mentions 'context entry' which aligns with context_id and 'question' which aligns with the question parameter, but adds no additional semantic meaning beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 the tool's purpose with specific verbs ('ask a question' and 'get a general second opinion') and identifies the target resource ('ChatGPT'). It distinguishes from some siblings like context_* and todo_* tools but doesn't explicitly differentiate from other AI assistants (ask_claude, ask_deepseek, ask_gemini).

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

Usage Guidelines3/5

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

The description implies when to use this tool (to ask ChatGPT about context entries or for general second opinions) but doesn't provide explicit guidance on when to choose ChatGPT over other AI assistants or when not to use it. No alternatives or exclusions are mentioned.

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/taylorleese/mcp-toolz'

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