Loading ToolBench
A Spring Boot-based MCP server providing tools for datetime retrieval and news headline fetching
This Spring AI MCP server exhibits significant definition quality gaps across all three tools. While tool names follow verb_noun conventions (good), descriptions are critically incomplete, parameters lack type information in schemas, and there is no documented output structure. The server leverages Spring AI's @Tool annotation for registration, but the underlying definitions are underspecified for LLM use. The avg tool definition score is 38/100, driven by missing parameter descriptions, minimal tool descriptions (under 50 chars each), and complete absence of output schema documentation.
Get Current date and time for user's timezone
Get Current date and time for user's timezone
Get current news haedlines for specific topic
Tool descriptions are trivially short (all <30 chars) and lack actionable context. 'Get current news headlines for specific topic' is vague about format, data structure, or when to use this vs other tools.
Parameter 'timezone' in getCurrentDateAndTimeTimeZoned has a description but NO type definition visible in the source code schema registration. The DateTimeTool.java shows @Tool annotation without explicit JSON Schema parameter metadata.
Parameter 'topic' in getNewsHeadlines has a description but NO visible type schema (string type is stated in the description but not in a structured schema). Spring AI's annotation processing may infer String, but this is not explicit in the provided code.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 33 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 0 | - | v1 |
No output schema documented for any tool. It is unclear what fields/structure the LLM should expect from getCurrentDateAndTime (timestamp format?), getCurrentDateAndTimeTimeZoned (same?), or getNewsHeadlines (array of articles with which fields?).
API key hardcoded as placeholder '<YOUR API KEY>' in NewsTool.java. This is a security anti-pattern. Credentials must be injected server-side via environment variables, never exposed in code or tool parameters.
No error handling guidance. If timezone is invalid (e.g., 'InvalidZone'), getCurrentDateAndTimeTimeZoned will throw an exception. No recovery hint provided to the LLM. If news API fails or rate-limits, getNewsHeadlines returns raw API response (or null). No categorization of retryable vs fatal errors.
getCurrentDateAndTime has no parameters but description says 'for user's timezone', this is misleading. It actually returns local/system timezone (via ZonedDateTime.now() without arguments). Description must clarify it uses the server's timezone, not user preference.
getNewsHeadlines description has typo: 'haedlines' instead of 'headlines'. While minor, this signals lack of review and reduces LLM confidence in tool quality.