Loading ToolBench
Example MCP server for Autodesk Platform Services with Auth0 authentication and APS OAuth integration
Two tools with minimal parameter documentation and no visible output schemas. Tool names follow verb_noun convention (get_*), but descriptions lack depth on WHEN to use each tool and what downstream actions they enable. No parameter descriptions visible for get-project-issues' projectId. No error handling guidance. Schemas present but incomplete, missing output documentation critical for agent chaining.
Retrieves all Autodesk Forma (formerly Autodesk Construction Cloud) hubs and projects accessible to the signed-in user.
Retrieves all issues in an Autodesk Forma (formerly Autodesk Construction Cloud) project.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., project IDs for chaining). get-hubs-projects and get-project-issues lack return type definitions.
Parameter descriptions missing. get-project-issues accepts projectId but provides no description of format, constraints, or whether the 'b.' prefix stripping is automatic or required from the caller.
Tool descriptions are generic and lack WHEN/WHY guidance. 'Retrieves all Autodesk Forma hubs and projects' does not explain when to call this vs other discovery tools, or what the agent should do with the results.
No error handling guidance. If a project ID is invalid or user lacks permissions, the tools provide no recovery hints (e.g., 'Try get-hubs-projects first to list valid projects').
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
No pagination or result limits documented. If hubs/projects or issues lists are large, no indication of how many results are returned or whether pagination is supported.