torbjorn/my-pal-mcp-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: refactored and tweaked model descriptions / schema to use fewer tokens at launch (average reduction per field description: 60-80%) without sacrificing tool effectiveness

Browse Source 
Disabled secondary tools by default (for new installations), updated README.md with instructions on how to enable these in .env
run-server.sh now displays disabled / enabled tools (when DISABLED_TOOLS is set)
This commit is contained in:
Fahad
2025-08-22 09:23:59 +04:00
parent 6921616db3
commit 4b202f5d1d
31 changed files with 409 additions and 609 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
tools/consensus.py
View File

@@ -37,12 +37,9 @@ logger = logging.getLogger(__name__)
# Tool-specific field descriptions for consensus workflow
CONSENSUS_WORKFLOW_FIELD_DESCRIPTIONS = {
"step": (
"In step 1: Provide the EXACT question or proposal that ALL models will evaluate. This should be phrased as a clear "
"question or problem statement, NOT as 'I will analyze...' or 'Let me examine...'. For example: 'Should we build a "
"search component in SwiftUI for use in an AppKit app?' or 'Evaluate the proposal to migrate our database from MySQL "
"to PostgreSQL'. This exact text will be sent to all models for their independent evaluation. "
"In subsequent steps (2+): This field is for internal tracking only - you can provide notes about the model response "
"you just received. This will NOT be sent to other models (they all receive the original proposal from step 1)."
"The core question for consensus. Step 1: Provide the EXACT proposal for all models to evaluate. "
"CRITICAL: This text is sent to all models and must be a clear question, not a self-referential statement "
"(e.g., use 'Evaluate...' not 'I will evaluate...'). Steps 2+: Internal notes on the last model's response; this is NOT sent to other models."
),
"step_number": (
"The index of the current step in the consensus workflow, beginning at 1. Step 1 is your analysis, "
@@ -55,11 +52,9 @@ CONSENSUS_WORKFLOW_FIELD_DESCRIPTIONS = {
),
"next_step_required": ("Set to true if more models need to be consulted. False when ready for final synthesis."),
"findings": (
"In step 1: Provide YOUR OWN comprehensive analysis of the proposal/question. This is where you share your "
"independent evaluation, considering technical feasibility, risks, benefits, and alternatives. This analysis "
"is NOT sent to other models - it's recorded for the final synthesis. "
"In steps 2+: Summarize the key points from the model response received, noting agreements and disagreements "
"with previous analyses."
"Your analysis of the consensus topic. Step 1: Your independent, comprehensive analysis of the proposal. "
"CRITICAL: This is for the final synthesis and is NOT sent to the other models. "
"Steps 2+: A summary of the key points from the most recent model's response."
),
"relevant_files": (
"Files that are relevant to the consensus analysis. Include files that help understand the proposal, "