Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Oct 28, 2025

Cloud agent has begun work on Contextual Tool Naming for LLM Reminders and will update this pull request as work progresses.

Original prompt

i would like it exposed as something that will hint the llm to search for context about the user including goals, mission statements, and reminders. The note headings will be a clue to what is useful. So if for example user asks about names, it will use names to remember list.. if the usrer asks about clothes there may be a waist measurement for fit (this is a just en EXAMPE do not overfit my examples)

[Chronological Review: The conversation began with the user expressing a desire to set up tool names and descriptions for a Notion MCP server to assist an LLM in searching for context about reminders. The user provided examples of how this could work, such as searching for names or clothing measurements. The user then reiterated their request for the LLM to use headings in notes as clues for useful information.]

[Intent Mapping:

  1. "i would like it exposed as something that will hint the llm to search for context about the user including goals, mission statements, and reminders." - The user wants to enhance the LLM's ability to retrieve relevant information based on user context.
  2. "The note headings will be a clue to what is useful." - The user intends to use note headings to guide the LLM's search for information.
  3. "if for example user asks about names, it will use names to remember list." - The user wants specific queries to trigger relevant searches in the Notion database.]

[Technical Inventory:

  • Tool: Notion MCP server
  • Purpose: To expose tools for searching and retrieving user context, including goals and reminders.
  • Key Functions: notion_search, notion_retrieve_page, notion_create_page, etc.]

[Code Archaeology: The user is working with the notion_server.py file, which contains various functions to interact with the Notion API, including searching for pages and retrieving metadata.]

[Progress Assessment: The user has outlined their goals for the Notion MCP server but has not yet implemented specific changes or configurations to achieve these goals.]

[Context Validation: The user’s intent to enhance the LLM's contextual understanding through structured note headings is clear and requires further implementation in the existing Notion MCP server.]

[Recent Commands Analysis:

  • Last Agent Commands: The user requested to expose the Notion MCP server tools to hint the LLM for context searches.
  • Tool Results Summary: No specific tool results were generated as the conversation focused on user intent rather than executing commands.
  • Pre-Summary State: The agent was actively discussing how to structure the Notion MCP server to facilitate better context retrieval for the LLM when the token budget was exceeded.
  • Operation Context: The user’s commands were aimed at improving the LLM's ability to search for and retrieve relevant user information based on specific queries.]
1. Conversation Overview: - Primary Objectives: The user aims to set up the Notion MCP server tools to assist an LLM in searching for context about user goals, mission statements, and reminders. They want to use note headings as clues for relevant information retrieval. - Session Context: The conversation has focused on how to structure the Notion MCP server to enhance the LLM's contextual understanding, with examples provided by the user. - User Intent Evolution: The user has consistently emphasized the need for the LLM to utilize structured note headings to improve search relevance.
  1. Technical Foundation:
  • Notion MCP Server: A custom server that interacts with the Notion API to manage notes and reminders.
  1. Codebase Status:
  • File Name: notion_server.py
  • Purpose: To provide an interface for interacting with the Notion API, including searching and retrieving notes.
  • Current State: The user is considering how to expose tools for better context retrieval but has not yet made specific code changes.
  • Key Code Segments: Functions for searching and retrieving pages from Notion.
  • Dependencies: Relies on the Notion API for data retrieval.
  1. Problem Resolution:
  • Issues Encountered: None explicitly stated, but the user is seeking to improve the LLM's contextual search capabilities.
  • Solutions Implemented: No solutions have been implemented yet; the user is in the planning phase.
  1. Progress Tracking:
  • Completed Tasks: None reported.
  • Partially Complete Work: User has outlined goals for the Notion MCP server.
  • Validated Outcomes: None yet, as implementation is pending.
  1. Active Work State:
  • Current Focus: Structuring the Notion MCP server to enhance LLM context retrieval.
  • Recent Context: The user has been discussing how to utilize note headings for effective searches.
  • Working Code: No specific code modifications were discussed recently.
  • Immediate Context: The user is looking to implement a system that allows the LLM to search for context based on user queries.
  1. Recent Operations:
  • Last Agent Commands: The user requested to expose the Notion MCP server tools for L...

Created from VS Code via the GitHub Pull Request extension.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

@jck411 jck411 marked this pull request as ready for review October 28, 2025 03:44
Copilot AI review requested due to automatic review settings October 28, 2025 03:44
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

@jck411 jck411 merged commit 9c0b56f into master Oct 28, 2025
1 check failed
Copilot AI requested a review from jck411 October 28, 2025 03:44
@jck411 jck411 deleted the copilot/expose-user-context-info branch October 28, 2025 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants