MCP server that exposes Composio tools for integrating with various applications like Gmail, Google Tasks, Google Calendar, Google Drive, Google Sheets, Google Docs, and Google Maps
Critical failures across all dimensions. The server exposes a single tool 'dynamic_composio_tools' with a generic, non-descriptive name that violates verb_noun naming conventions. The tool description is vague and does not explain WHAT it does, WHEN to use it, or what it returns. Input schema is severely underspecified: 'params' is an object with no type constraints, no enum values, no min/max bounds, and no per-parameter descriptions. No output schema is documented. Error handling is minimal (generic 'An error occurred' message). The tool name itself is a red flag, 'dynamic_composio_tools' is not an action verb; it should be something like 'execute_composio_action' or 'run_composio_tool'. The design conflates tool discovery with execution, forcing the LLM to guess which Composio action to invoke without structured guidance.
Tools are dynamically loaded from Composio apps (GMAIL, GOOGLETASKS, GOOGLECALENDAR, GOOGLEDRIVE, GOOGLESHEETS, GOOGLEDOCS, GOOGLE_MAPS or custom apps via COMPOSIO_APPS environment variable). Each tool's name and description come from the Composio action metadata.
Tool name 'dynamic_composio_tools' is not an action verb and does not follow verb_noun convention. LLMs cannot infer intent from the name alone. Should be 'execute_composio_action' or similar.
Input schema completely lacks parameter descriptions and type constraints. 'params' is defined as a bare object with no properties, enums, or validation rules. LLMs cannot determine what fields to pass or what values are valid.
No output schema documented. LLMs do not know what fields to expect in the response, making it impossible to chain this tool with others or extract specific data.
Tool description is generic and does not explain WHAT the tool does, WHEN to use it, or what it returns. 'Tools are dynamically loaded...' is metadata, not a user-facing description. Should state: 'Execute a Composio action (e.g., send email, create calendar event). Provide the action name and parameters. Returns the action result as JSON.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 21 | 2026-07-28+ | v2 |
Error handling is minimal and non-actionable. Generic 'An error occurred while executing the tool' message gives the LLM no guidance on retry, recovery, or root cause. Should categorize errors (retryable, user-fixable, fatal) and include the invalid value and constraint violated.