Loading ToolBench

Reading the current corpus…

tasklite-mcp MCP server · B · ToolBench

tasklite-mcp

TaskLite MCP server: build a full backend (projects, boards, data, REST endpoints), deploy a frontend onto it, and get a ready-made admin, from Claude Code and other MCP clients

2026-07-28+STDIO37 tools

71/100

Definition Quality81

Protocol Readiness47

SupportabilityNot measured-

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: stateless requests

Current-spec patterns detected

Summary

TaskLite MCP has 37 well-named tools with consistent verb_noun patterns (create_*, list_*, delete_*, etc.). All tools have descriptions and input schemas are present. However, many parameter descriptions are minimal (under 50 chars), output schemas are not documented, and error handling lacks recovery guidance. Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are declared in ANNOTATIONS constant but not visible in all tool registrations. The server sanitizes sensitive user fields (resetPasswordToken, googleId, mfaEnabled) before returning responses, which is good security practice. Composition is sound, tools chain well (e.g., list_projects → create_board → query_items). Main gaps: parameter constraints (enums, ranges) are sparse, descriptions don't explain WHEN to use each tool vs. similar ones, and output field documentation is absent.

Tools (37)

add_commentwriteauthsource verified82/100

Add comment to an item

configure_external_accesswriteauthsource verified75/100

Configure external user access

connectwritesource verified78/100

Connect or switch TaskLite account

connection_statusread onlysource verified90/100

Check TaskLite connection

create_appwriteauthsource verified85/100

Create app

create_app_api_keywriteauthsource verified82/100

Create app API key

create_app_endpointwriteauthsource verified78/100

Create app endpoint

create_automationwrite

Issues (5)

HIGHtool ↗

Output schemas not documented. Tools return JSON but LLMs cannot see what fields to expect (e.g., does list_projects return {id, name, description, owner} or {projectId, projectName, ...}?). This forces agents to guess field names and breaks downstream tool chaining.

list_organizationslist_projectsquery_itemslist_commentssearchexport_project

HIGHconstrained-input ↗

Parameter descriptions lack constraints and format guidance. E.g., 'registrationPolicy' accepts 'open', 'approval', or 'closed' but description doesn't state this as an enum. 'limit' and 'offset' in query_items have no min/max bounds. LLMs cannot validate inputs without explicit constraints.

configure_external_accessquery_itemscreate_columncreate_app_endpoint

HIGHrecovery-guide ↗

Error handling lacks recovery guidance. No evidence of actionable error messages (e.g., 'User not found. Try search_users() first.'). Errors likely return raw API responses or stack traces, giving agents no path forward.

Recommendations

Document output schemas for all tools. Add a 'Returns' section to each tool description or a separate schema definition. Example: 'Returns {id: string, name: string, description: string, owner: {id, name}, createdAt: ISO8601}'. This enables LLMs to chain tools correctly.
Add enum constraints to parameters with fixed choices. For configure_external_access.registrationPolicy, declare: 'enum: ["open", "approval", "closed"]'. For create_column.type, list all 13 valid types explicitly in the schema.
Expand parameter descriptions to include format, range, and dependencies. E.g., 'limit (1 - 100, default 20): Maximum items per page' and 'offset (0+): Pagination offset; requires limit'. This matches the 72-char baseline for param annotations.
Implement actionable error messages. When a resource is not found, return available alternatives. E.g., 'Project "xyz" not found. Available projects: proj-a, proj-b, proj-c'. When input is invalid, echo the constraint: 'Invalid registrationPolicy: got "maybe", must be one of: open, approval, closed'.
Fix set_cell schema. Replace type:null with the actual union of valid types (string | number | boolean | array | object | null). Add description: 'New cell value. Type depends on column type (text→string, number→number, date→ISO8601, etc.). Pass null to clear the cell.'

Spec posture evidence

Inferred effective spec: 2026-07-28+.

Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)

Score history

Overall score trend

First recorded score · v2 rubric

71/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	B	71	2026-07-28+	v2