feat: add parameterless prompt execution support with defaults and auto-generated values #126
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…to-generated values
## Key Features Added
### 1. Enhanced Schema Support
- Add `default` property to PromptArgumentSchema for explicit default values
- Support for parameterless prompt execution with sensible defaults
### 2. Improved Parameter Handling
- MCPServer now passes empty object when arguments are undefined
- BasePrompt gracefully handles missing arguments with automatic defaults
- Automatic type-based defaults: string="", number=0, boolean=false, array=[], object={}
### 3. Smart Validation Logic
- Fields with explicit defaults are marked as not required in prompt definitions
- Optional parameters (required: false) bypass validation requirements
- Maintains full backward compatibility with existing prompts
### 4. Comprehensive Testing
- 12 test cases covering all parameterless execution scenarios
- Tests for explicit defaults, automatic defaults, and optional parameters
- Error handling and edge case validation
### 5. Rich Documentation
- Complete Prompts section in README with examples and best practices
- Migration guide for existing prompts
- Usage patterns for different parameter configurations
## Breaking Changes
None - fully backward compatible
## Usage Examples
**Before**: `/my-prompt (MCP) {"message": ""}` (required empty object)
**After**: `/my-prompt (MCP)` (truly parameterless execution)
This enables natural prompt usage like `/gitlab:commit (MCP)` without requiring empty JSON objects.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
- Update package name to @sekora/mcp-framework for scoped npm publishing - Add publish.yml workflow that triggers on GitHub releases and manual dispatch - Include comprehensive CI steps: linting, testing, building before publishing - Support manual version updates and automatic npm publishing with public access - Enhance release.yml workflow with outputs for better integration 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
…--components--mcp-framework chore: release 0.2.16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Key Features Added
1. Enhanced Schema Support
defaultproperty to PromptArgumentSchema for explicit default values2. Improved Parameter Handling
3. Smart Validation Logic
4. Comprehensive Testing
5. Rich Documentation
Breaking Changes
None - fully backward compatible
Usage Examples
Before:
/my-prompt (MCP) {"message": ""}(required empty object)After:
/my-prompt (MCP)(truly parameterless execution)This enables natural prompt usage like
/gitlab:commit (MCP)without requiring empty JSON objects.🤖 Generated with Claude Code