[MCP] Add the Create_Record Built in tool

[aaronburtle]

Why make this change?

Closes #2828

By adding the Create_Record tool to the MCP endpoint.

What is this change?

Add a built in tool, Create_Record which uses the rest infrastructure to form and validate the query needed to complete a create action. Behavior is at parity with the rest equivalent create operation.

How was this tested?

Manually tested Insomnia using post.

Sample Request(s)

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "create_record",
    "arguments": {
      "entity": "Broker",
      "data": {
        "ID Number": 3,
				"First Name": "Michael",
				"Last Name": "Jordan"
      }
    }
  }
}
 

[Copilot]

Pull Request Overview

This PR adds a new built-in tool called Create_Record to the MCP (Model Context Protocol) endpoint, enabling record creation functionality through the MCP interface. The implementation leverages the existing REST infrastructure for query formation and validation while maintaining parity with the REST equivalent create operation.

• Implements comprehensive create record functionality with proper validation and authorization
• Integrates with existing DAB services including metadata providers, authorization resolvers, and mutation engines
• Provides detailed error handling and logging for various failure scenarios

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[anushakolan]

The current PR description only covers the success case. Since the tool should also be validated against edge cases and other standard scenarios, I recommend expanding the testing section to include details on the various test cases executed to confirm the tool’s expected behavior.

[anushakolan]

The unit tests are failing, please run dotnet format and that should fix most of the syntax issues.

[anushakolan]

The unit tests are failing because of formatting issues, fix the formatting and re-run the tests. Approving the changes to unblock the PR, but waiting on

1. confirming if the tool response matches the REST create record response.
2. All tests are successfully passing.

[aaronburtle]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[Aniruddh25]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[aaronburtle]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).