Adds the ability to define tool parameters in json schema directly

Motivation and Context

Fixes #283

The typescript-sdk uses Zod to validate the parameters passed to tools and generates a json schema representation from it for the MCP client. There are cases where you might want to define tools directly with a JSON Schema: for example, when generating mcp tools dynamically from an OpenAPI Specification (example here). In these cases, you have to go from json schema, to Zod and back to json schema which is wasteful and hard to do without losing information along the way (for example, when you have recursive types).

Example usage

mcpServer.tool({
  name: "hello",
  paramsSchema: {
    type: "object",
    properties: { name: { type: "string" } },
    additionalProperties: false
  },
  cb: async (args) => ({
    content: [{ type: "text", text: `Hello, ${args.name}!` }]
  })
});

How Has This Been Tested?

• Existing tests are still passing ✅
• Added a test to make sure the new tool definition signature works correctly ✅
• Added a test to make sure tool arg validation works correctly ✅
• Tested a dummy tool defined with JSON Schema in Claude Desktop ✅

Breaking Changes

None, the changes are intended to only be additive.

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 Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

• When using JSON Schema, you lose the ability to properly type the tool args (which is just marked as object).
• I added ajv as a dependency, which seems to be the reference when working with JSON Schema in Node.js
• I added a new function overload for MCPServer#tool() which accepts a configuration object instead of positional arguments. I only did that because I struggled to make the types work with positional arguments. Notably, I was losing type inference with the ToolCallback conditional type. Typescript does seem to infer types correctly when using the object version though. And while I understand it's completely subjective, I think having an object version makes for a nicer API (without removing previous options) and it would address Allow passing a Tool object to the server.tool() method #369
• Moved some functions around in mcp.ts to keep the methods from growing too much from the additional complexity