Loading ToolBench
Model Context Protocol server for the JobBOSS² Public API
Server has solid schema definitions and clear naming conventions. All 9 tools have descriptions and input schemas with proper types. However, descriptions are often generic (e.g., jobboss2_undocumented_operation lacks actionable guidance), parameter descriptions lack constraint details (format, range, valid values), and error handling guidance is minimal. Output schemas are not documented. Tool composition is reasonable but some tools (describe_resource, undocumented_operation) are overly broad. No evidence of idempotency guarantees or recovery guidance in error cases.
Create a JobBOSS2 record. Request data is checked against ECI's OpenAPI schema. Use jobboss2_describe_resource first to inspect required parent keys and fields.
List JobBOSS2 resources or inspect one resource's paths, keys, query parameters, and request schema. Call this before create or update tools.
Get one JobBOSS2 record. Use jobboss2_describe_resource to find the exact key names required by the resource.
List issuing-materials lookup data for a specific operation
List a JobBOSS2 resource with documented fields, filters, sorting, and offset paging. Filter keys use field[operator], where operator is eq, ne, gte, lte, gt, lt, in, notin, or null.
Create a JobBOSS2 report
jobboss2_undocumented_operation violates single-responsibility principle. Accepts arbitrary operation names, path/query/body parameters with no schema validation. LLM cannot determine valid inputs or expected outputs. Name 'undocumented' signals incomplete API coverage.
Parameter descriptions lack constraint details. 'operation' enum values not documented in descriptions. 'take' parameter has max=200 in schema but description doesn't explain the limit or why. 'filters' object structure not explained (field[operator] syntax buried in jobboss2_list description, not in parameter docs).
Output schemas not documented. Tools return ApiResult or JsonObject but LLM has no guidance on expected fields, structure, or how to chain results to downstream tools. E.g., does jobboss2_create return the created record ID? Required for tool composition.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2025-06-18+ | v2 |
Get a JobBOSS2 report
Call an undocumented JobBOSS2 API operation
Patch a JobBOSS2 record. Request data is checked against ECI's OpenAPI schema. Use jobboss2_describe_resource first to inspect key names and writable fields.
Error handling lacks recovery guidance. No evidence of actionable error messages (e.g., 'Invalid filter: field[operator] syntax required'). JobBoss2InputError thrown but LLM receives no hint on how to correct input or which tool to call next.
jobboss2_issuing_materials_lookup, jobboss2_reports_get, jobboss2_reports_create have minimal descriptions (under 50 chars). Insufficient context for LLM to determine when to call them vs similar tools. E.g., 'Get a JobBOSS2 report' doesn't explain prerequisites or what data is returned.