Loading ToolBench
Spring AI MCP server that enables interaction with a Cloud Foundry foundation
16 tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. All tools have descriptions (10-50 chars, below the 50-200 char baseline for LLM optimization). Input schemas present but sparse: most parameters lack detailed constraints, ranges, or format guidance. No output schemas documented. No error recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Naming is verb-noun compliant (applicationsList, pushApplication, deleteApplication) but descriptions are terse and lack WHEN/WHY context. Parameter descriptions exist but are minimal (e.g., 'Name of the Cloud Foundry application' repeated 16 times). No pagination, no batch operations, no idempotency guidance.
Gets detailed information about a Cloud Foundry application
Return the applications (apps) in my Cloud Foundry space
Bind a service instance to a Cloud Foundry application
Delete a Cloud Foundry application
Return the organizations (orgs) in my Cloud Foundry foundation
Push an application JAR file to the Cloud Foundry space.
Restart a running Cloud Foundry application
Descriptions are terse (10-50 chars) and lack WHEN/WHY context. LLM cannot determine when to select 'applicationDetails' vs 'applicationsList' or understand prerequisites. Baseline for A+ tools is 50-200 chars with explicit selection guidance.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., does applicationsList return app IDs for use in applicationDetails?). All 16 tools lack return type documentation.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Scale the number of instances, memory, or disk size of an application.
Get detailed information about a service instance in my Cloud Foundry space
Return the service instances (SIs) in my Cloud Foundry space
Return the service offerings available to me in the Cloud Foundry marketplace
Get the space quota for my Cloud Foundry space
Return the spaces in my Cloud Foundry organization
Start a Cloud Foundry application
Stop a running Cloud Foundry application
Unbind a service instance from a Cloud Foundry application
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLM cannot distinguish safe reads from destructive writes. deleteApplication, pushApplication, scaleApplication marked DESTRUCTIVE/WRITE in metadata but not in schema annotations.
Parameter descriptions are generic and repeated. 'Name of the Cloud Foundry application' appears 16 times without format guidance, constraints, or examples. No min/max length, no regex patterns, no enum constraints for optional fields like 'noStart' (boolean).
No error handling guidance. Tools like deleteApplication (DESTRUCTIVE) and pushApplication (WRITE) lack confirmation patterns, dry-run options, or recovery guidance. No documentation of what errors are retryable vs fatal.