fix(sequential-thinking): Keep case of json params and description same

[jnick26]

Models are confused about the case of the variables, which results into random validation errors. Keeping them the same helps to remove back and forth.

Description

Server Details

• Server: sequential-thinking
• Changes to: prompts

Motivation and Context

At random model may choose to pass either camel or snake_case names of keys in the request. Seems that model is confused, as required and

How Has This Been Tested?

I've reproduced this problem in Claude Code (Sonnet 4.5) and Copilot CLI (Sonnet 4.5, GPT-5).

Breaking Changes

Don't think it is a breaking change. If some clients did not have issues, most probably they will be even better with it.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options