Loading ToolBench

Reading the current corpus…

node-red-mcp-server MCP server · F · ToolBench

node-red-mcp-server

github.com/moises-paschoalick/node-red-mcp-server

Node-RED integration with Model Context Protocol (MCP) servers for executing MCP tools and resources through Node-RED flows

2026-07-28+STDIO7 tools

41/100

Definition Quality41

Protocol Readiness50

Supportability34

Spec posture

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

Static source inference · medium confidence

Current-spec patterns detected

Summary

Server has 7 tools with significant quality gaps. Three tools (Hello, Time, Weather) have empty input schemas and trivial descriptions (10-50 chars), violating hard rules. Google Drive/Sheets tools have better schemas but lack parameter descriptions and output documentation. No tool has documented return types or error recovery guidance. Naming is inconsistent: 'Hello Tool' vs verb_noun pattern. No tool annotations (readOnlyHint/destructiveHint). Overall structure is present but execution is poor.

Tools (7)

Hello Toolread onlysource verified12/100

Responds with a hello world message

Time Toolread onlysource verified12/100

Returns the current local time

Weather Toolread onlysource verified15/100

Fetches current weather data for São Paulo

gdrive_read_fileread onlyauthsource verified63/100

Read contents of a file from Google Drive

gdrive_searchread onlyauthsource verified58/100

Search for files in Google Drive

gsheets_readread onlyauthsource verified65/100

Read data from a Google Spreadsheet with flexible options for ranges and formatting

gsheets_update_cellwriteauthsource verified60/100

Update a cell value in a Google Spreadsheet

Issues (5)

CRITICALtool-description ↗

Three tools (Hello, Time, Weather) have empty input schemas and descriptions under 20 chars, violating hard scoring rules. These must be removed or completely redesigned.

Hello ToolTime ToolWeather Tool

CRITICALresponse-shaper ↗

No tool has documented output/return schema. LLMs cannot plan downstream calls or extract required fields. All tools need explicit response documentation.

gdrive_searchgdrive_read_filegsheets_update_cellgsheets_read

HIGHtool-description ↗

Google Drive/Sheets tools lack parameter descriptions. 'query', 'pageToken', 'pageSize', 'range', 'value' have no guidance on format, constraints, or valid values.

gdrive_searchgdrive_read_filegsheets_update_cellgsheets_read

HIGHrecovery-guide ↗

Recommendations

Remove or redesign Hello, Time, Weather tools. If kept, expand descriptions to 50+ chars and add meaningful input schemas (e.g., timezone parameter for Time).
Document output schema for all tools. Example: gdrive_search should return {files: [{id, name, mimeType, webViewLink}], nextPageToken?, totalResults?}.
Add parameter descriptions to Google Drive/Sheets tools. Specify format (A1 notation for range), constraints (pageSize 1-100), and examples in descriptions, not as example values.
Implement error recovery guidance. E.g., 'If file not found, call gdrive_search() with partial name to locate it.' Add error classification (retryable vs user-fixable).
Add tool annotations: mark gdrive_search/gdrive_read_file/gsheets_read with readOnlyHint=true; mark gsheets_update_cell with destructiveHint=true and idempotentHint=false.

Score history

Overall score trend

First recorded score · v2 rubric

41/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	41	2026-07-28+	v2