Loading ToolBench

Reading the current corpus…

mcp-server-monday-qi MCP server · F · ToolBench

← Browse

mcp-server-monday-qi

github.com/YajieQi123/mcp-server-monday-qi

MCP Server for monday.com integration, providing tools to manage boards, items, groups, documents, and updates

<=2025-11-25STDIO21 tools

47/100

Definition Quality59

Protocol Readiness47

Supportability28

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

Server has 21 tools with complete input schemas and descriptions present for all tools. However, quality is inconsistent: naming is verb-forward and clear (good), but many parameter descriptions lack detail on constraints, formats, and valid ranges. Output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages visible in code. Parameter descriptions average ~40 chars, well below the 72-char baseline for A+ tools. Several tools have underdescribed parameters (e.g., monday-create-update missing itemId description; monday-list-items-in-groups has a Chinese-language description fragment). No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Composition is reasonable, tools are single-purpose, but some could be more discoverable (e.g., monday-get-item-updates vs monday-get-update-files naming is similar and could confuse LLMs).

Tools (21)

monday-add-doc-blockwriteauthsource verified75/100

Add a block to a Monday.com document

monday-archive-itemreversibleauth50/100

Archive an item in a Monday.com board

monday-create-boardwriteauth50/100

Create a new Monday.com board

monday-create-board-groupwriteauth50/100

Create a new group in a Monday.com board

monday-create-docwriteauth50/100

Create a new document in Monday.com. Specify either workspace_id (with kind, name) or board_id (with column_id, item_id) as the location.

monday-create-itemwriteauth50/100

Create a new item in a Monday.com Board. Optionally, specify the parent Item ID to create a Sub-item.

monday-create-updatewriteauth50/100

Create an update (comment) on a Monday.com Item or Sub-item.

monday-delete-item

Issues (5)

CRITICALtool ↗

Missing output schema documentation. No tool documents what fields are returned, their types, or structure. LLMs cannot plan downstream calls or extract required data without knowing response shape.

monday-create-itemmonday-get-items-by-idmonday-update-itemmonday-list-boardsmonday-list-items-in-groups

HIGHconstrained-input ↗

Parameter descriptions lack constraint details. 'columnValues' is described as 'Dictionary of column values' but does not specify format, valid keys, or value types. 'limit' and 'page' parameters lack min/max bounds.

monday-create-itemmonday-update-itemmonday-list-boardsmonday-list-items-in-groups

HIGHtool-annotations ↗

No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. Destructive tools (monday-delete-item, monday-archive-item) and write tools lack annotations to guide agent behavior.

monday-delete-itemmonday-archive-itemmonday-create-item

Recommendations

Add output schema documentation to every tool. Document return type (object/array), field names, types, and which fields are required. Example: monday-list-boards should document it returns {boards: [{id, name, owner, created_at}], total_count, has_more}.
Add min/max constraints to numeric parameters. E.g., limit: 1-100 (default 20), page: 1+, days: 1-365. Include these in parameter descriptions, not just JSON Schema.
Implement tool annotations. Mark monday-delete-item and monday-archive-item with destructiveHint=true. Mark read-only tools (monday-get-*) with readOnlyHint=true. Mark idempotent tools with idempotentHint=true.
Expand parameter descriptions to 50-100 chars with format/constraint details. E.g., 'columnValues: Object mapping column IDs to values. Column IDs are strings like "status", "priority". Values depend on column type (text, select, date, etc.).'
Add error handling guidance to tool descriptions. E.g., 'Returns 404 if item not found, try monday-list-items-in-groups to verify the item exists. Returns 403 if user lacks board access.'

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

47/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	47	<=2025-11-25	v2