MCP server for NoCoDB operations with natural language interface
Server has 29 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-50 chars, mostly generic), and input schemas are present with type definitions. However, descriptions are uniformly terse and lack actionable context for LLM selection. Parameter descriptions are minimal (e.g., 'The ID of the base' repeated across tools). No output schemas documented. No error handling guidance. No tool annotations (readOnlyHint/destructiveHint). Naming is verb-noun compliant but lacks disambiguation for similar operations (e.g., create_base vs create_table vs create_column all follow same pattern without clear differentiation). No pagination guidance despite tools like get_table_data accepting limit/offset. Security: API token and Cloudflare credentials are injected server-side (good), but no audit logging or permission gates visible.
Create a new base.
Create a new column in a table.
Create a filter for a view.
Create a new record in a table.
Create a sort for a view.
Create a new table in a base.
Create a new view for a table.
Descriptions are uniformly terse (10-50 chars) and lack actionable context. Examples: 'List all bases in NoCoDB' (28 chars), 'Get detailed information about a specific base' (45 chars). Baseline for A+ tools is 50-200 chars with WHEN/WHY guidance. LLMs cannot distinguish between similar tools (create_base vs create_table vs create_column) based on these descriptions.
No output schemas documented. Tools return data but LLMs have no visibility into response structure. Example: get_table_data returns records but schema for record fields is undocumented. This forces LLMs to guess field names and types, increasing errors.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | <=2025-11-25 | v2 |
Create a webhook for a table.
Delete a column from a table.
Delete a filter.
Delete a record from a table.
Delete a sort.
Delete a table.
Delete a view.
Delete a webhook.
Duplicate a table with specified options.
Get detailed information about a specific base.
Get a specific record from a table.
Get data from a table.
Get detailed information about a table.
List all bases (projects) in NoCoDB.
List all filters for a view.
List all sorts for a view.
List all tables in a base.
List all views for a table.
List all webhooks for a table.
Test a webhook configuration.
Update an existing column.
Update a record in a table.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Risk field is present in metadata but not exposed to LLM via MCP tool annotations. Agents cannot distinguish safe reads from destructive operations without explicit hints.
Parameter descriptions are minimal and repetitive. Example: 'The ID of the base' appears in 5+ tools without explaining what a base is or when to use base_id vs table_id. Baseline is 50-100 chars per parameter with format/constraint guidance.
No error handling guidance. Tools accept generic 'object' parameters (column_data, view_data, filter_data, webhook_data) with no schema or validation hints. LLMs cannot know what fields are required or what values are valid. No recovery guidance if a call fails.