contextl 1.2.8 → 1.2.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/python/mcp_server.py +6 -13
package/package.json
CHANGED
package/python/mcp_server.py
CHANGED
|
@@ -71,19 +71,12 @@ async def list_tools() -> list[types.Tool]:
|
|
|
71
71
|
"query": {
|
|
72
72
|
"type": "string",
|
|
73
73
|
"description": (
|
|
74
|
-
"SYSTEM INSTRUCTION:
|
|
75
|
-
"
|
|
76
|
-
"
|
|
77
|
-
"
|
|
78
|
-
"
|
|
79
|
-
"
|
|
80
|
-
"3. Include Known Framework Terms: Append standard terminology of the framework.\n"
|
|
81
|
-
"4. Target File Types/Structures: Use terms like 'config', 'yaml', 'json' if looking for configurations.\n"
|
|
82
|
-
"5. Keep it space-separated: Output a single string of space-separated keywords without punctuation.\n\n"
|
|
83
|
-
"Examples:\n"
|
|
84
|
-
"- 'Where are the main react components and routing defined?' -> 'createRouter Route routeTree components layout'\n"
|
|
85
|
-
"- 'Find the application entry point and main method.' -> 'public static void main bootstrap init ApplicationContext configuration'\n"
|
|
86
|
-
"- 'How is the user authentication handled?' -> 'login auth authenticate jwt token session passport'"
|
|
74
|
+
"SYSTEM INSTRUCTION: The contextl search engine is highly optimized for both raw conversational queries AND exact keyword searches. "
|
|
75
|
+
"It uses dynamic structural multipliers to instantly rank classes for short/conversational queries, and switches to BM25 frequency math for longer keyword queries.\n\n"
|
|
76
|
+
"STRATEGY INSTRUCTION:\n"
|
|
77
|
+
"1. INITIAL SEARCHES: Pass the user's raw natural-language query directly. Do NOT convert it to keywords. The engine is smart enough to drop stop-words and find the primary class anchors. Example: 'where is the auth logic?' -> 'where is the auth logic?'\n"
|
|
78
|
+
"2. TARGETED DEBUG SEARCHES: If the initial search fails, or if you are deep into debugging and need to cross-reference very specific variables across the codebase, then convert the query into highly optimized, space-separated keywords. Example: 'auth failure bug' -> 'login jwt AuthController retry_count token'\n"
|
|
79
|
+
"Never append generic filler words to targeted searches."
|
|
87
80
|
),
|
|
88
81
|
},
|
|
89
82
|
"top_n": {
|