Users Online
· Guests Online: 20
· Members Online: 0
· Total Members: 232
· Newest Member: Zarfdrilhor
· Members Online: 0
· Total Members: 232
· Newest Member: Zarfdrilhor
Forum Threads
Newest Threads
No Threads created
Hottest Threads
No Threads created
Latest Articles
06_030. Handling Timestamp Parsing for MCP Tool Arguments.html
06_030. Handling Timestamp Parsing for MCP Tool Arguments.htmlAI TOOLS » Spring AI + MCP Build Distributed AI Systems with Java |
| Categories | Most Recent | Top Rated | Popular Courses |
�
| ||||
 | Uploader | Date Added | Views | Rating |
| Superadmin | 31.05.17 | 5 | No Rating | |
| Description | ||||
| 6 - Building the MCP Client Assistant - Spring AI + MCP Build Distributed AI Systems with Java Handling Timestamp Parsing for MCP Tool Arguments In the next lesson we will create a deployment using the MCP tool createDeployment. Depending on the language model output, you may encounter a timestamp parsing error when the tool is executed. Example Error Text '2026-03-13T20:30:00+05:30' could not be parsed, unparsed text found at index 19 This happens because the LLM may generate timestamps with timezone information, such as Z (UTC) or an offset like +05:30. However, our deployment service originally parses the value using LocalDateTime, which does not accept timezone offsets. Typical Timestamp Formats Generated by LLMs 2026-03-13T20:30:00 2026-03-13T20:30:00Z 2026-03-13T20:30:00+05:30 Only the first format works with LocalDateTime.parse(). Recommended Fix Update the MCP tool implementation in deployment-service to parse the timestamp using OffsetDateTime, and then convert it to LocalDateTime. LocalDateTime scheduled = OffsetDateTime.parse(scheduledTime).toLocalDateTime(); This approach safely handles all ISO-8601 timestamp formats that the LLM might generate. Updated MCP Tool Example @McpTool( name = "createDeployment", description = "Create a new deployment. Provide serviceName, environment (DEV, QA, PROD), scheduledTime and owner" ) public Deployment createDeployment(String serviceName, String environment, String scheduledTime, String owner) { LocalDateTime scheduled = OffsetDateTime.parse(scheduledTime).toLocalDateTime(); return deploymentService.createDeployment( serviceName, DeploymentEnvironment.valueOf(environment), scheduled, owner ); } After Applying This Fix Your deployment tool will correctly handle timestamps generated by the LLM, and the workflow demonstrated in the next lesson should execute successfully. | ||||
Ratings
Comments
No Comments have been Posted.
Post Comment
Please Login to Post a Comment.