Loading ToolBench
Serves governed capabilities as Spring AI tools (ToolCallbackProvider) so they are exposed over a live MCP server transport.
Single tool 'greet_v1' has minimal definition quality. Description is present but extremely brief (18 chars, below 20-char threshold). No output schema documented. Tool name lacks action verb clarity ('greet' is acceptable but 'v1' suffix is unusual and suggests versioning confusion). No error handling guidance. Overall, this is a toy/test tool with insufficient production-grade documentation.
Greets a person by name
Tool description is 18 characters ('Greets a person by name'), below 20-char minimum. Descriptions must be 10 - 1024 chars and explain WHAT, WHEN, and any prerequisites.
Input parameter 'name' has no description. LLMs cannot infer meaning from names alone.
No output schema documented. LLMs need to know what fields to expect in the response to plan downstream calls and extract data correctly.
Tool name 'greet_v1' includes version suffix. Versioning should be handled at the server level, not in individual tool names. Use 'greet' and manage versions via server capabilities.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | 2026-07-28+ | v2 |
No error handling guidance. Tool description does not explain what happens on failure or how the LLM should recover (e.g., if name is empty or invalid).