Loading ToolBench
MCP server for Jira ticket creation, Confluence retrieval, and ProductBoard notes
TeamFlow MCP has well-structured tool definitions with consistent naming (verb_noun pattern), complete input schemas with types and descriptions, and clear parameter constraints (enums, patterns, limits). However, tool descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool vs. alternatives. Output schemas are not documented, LLMs cannot plan downstream calls. Error handling is absent from visible code. Security: credentials injected server-side (good), but no audit logging visible. Composition is sound: tools are single-responsibility and chainable (e.g., search → get → create workflows). Average tool score: 68/100.
Retrieves the full content of a Confluence page by its numeric page ID.
Lists all accessible Confluence spaces. Returns space key, name, type, and URL.
Searches Confluence using CQL (Confluence Query Language). Returns matching pages with title, excerpt, space, and URL.
Creates a Jira issue in project. Allowed issue types are configurable.
Retrieves details for a single Jira issue by its key (e.g. TEAM-42).
Searches Jira issues scoped to project. Provide optional JQL filters (status, issuetype, assignee, etc.) which are AND-ed with the project constraint.
Output schemas not documented. LLMs cannot infer what fields are returned or plan downstream tool calls. E.g., jira_create_ticket returns a JiraIssue but the response structure is not visible in tool definitions.
Tool descriptions are generic and lack LLM-optimized guidance. E.g., 'Lists all accessible Confluence spaces' does not explain WHEN to call this vs. search_content, or what the agent should do with the results. Descriptions should be 50-200 chars and answer: what, when, why.
No error handling guidance visible. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next. E.g., if jira_create_ticket fails due to invalid issue type, the error should suggest calling jira_list_tickets to discover valid types.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | B | 79 | 2026-07-28+ | v2 |
Creates a note in ProductBoard grouped under the configured source. Use this to capture customer feedback, feature requests, or observations.
Lists features from ProductBoard. Use this to understand the product backlog and link notes to existing features.
Lists notes from ProductBoard. Results include all notes; filter by the configured source is applied automatically on the source field.
No audit logging visible in source. Agent-initiated writes (jira_create_ticket, pb_create_note) should log who called what, with which parameters, and what happened. Required for compliance and incident response.
Destructive operations (jira_create_ticket, pb_create_note) lack confirmation or dry-run support. Agents make mistakes, a confirm_before_execute pattern would prevent accidental ticket creation or note spam.