fix(mcp): clarify Codex tool can implement changes, not just answer questions
The Codex MCP tool description was misleading - it said "Ask a question" and "Returns a thoughtful response" which implied it was read-only. In reality, Codex has full filesystem access and can create/modify files directly since the MCP server executes the `codex` CLI agent which has full implementation capabilities. **Changes:** - Updated description to clarify Codex can "implement changes or answer questions" - Added note that "Codex has full filesystem access and can create/modify files directly" - Updated inputSchema description from "question" to "question or implementation task" - Updated comment from "for initial questions" to "for both questions and implementation" This prevents confusion about Codex being a read-only Q&A tool when it's actually a full implementation agent.
This commit is contained in:
parent
a4cd3a275e
commit
3250de8f6d
1 changed files with 3 additions and 3 deletions
|
|
@ -21,14 +21,14 @@ const server = new McpServer({
|
|||
version: "1.0.0",
|
||||
});
|
||||
|
||||
// Register the codex tool for initial questions
|
||||
// Register the codex tool for both questions and implementation
|
||||
server.registerTool(
|
||||
"codex",
|
||||
{
|
||||
title: "Codex AI Assistant",
|
||||
description: "Ask a question to OpenAI Codex AI assistant. Returns a thoughtful response. Use this for architectural decisions, code review, and technical consultation.",
|
||||
description: "Ask OpenAI Codex to implement changes or answer questions. Codex has full filesystem access and can create/modify files directly. Use this for architectural decisions, code review, technical consultation, and implementation tasks.",
|
||||
inputSchema: {
|
||||
question: z.string().describe("The question to ask Codex"),
|
||||
question: z.string().describe("The question or implementation task for Codex"),
|
||||
conversationId: z.string().optional().describe("Optional conversation ID to maintain context across calls"),
|
||||
},
|
||||
},
|
||||
|
|
|
|||
Loading…
Reference in a new issue