Static source inference · medium confidence · detected: Logging
Deprecated protocol patterns detected
Summary
The Quickbase MCP server has 25 tools with inconsistent definition quality. Tools have basic descriptions and some have schemas, but many lack detailed parameter descriptions, lack proper error handling guidance, and have generic or minimal descriptions. The server follows a verb_noun naming convention well (e.g., create_app, query_records, delete_field), but parameter documentation is sparse. Only 4 of 25 tools show explicit input schemas in the provided source; most parameter details are inferred rather than directly visible. Error handling is minimal, no guidance on recovery steps, categorization, or actionable error messages. Several tools (check_configuration, test_connection, configure_cache) have empty or missing input schemas. No evidence of tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite risk classifications being declared. Output schemas are not documented in the tool definitions.
Tools (25)
bulk_create_recordswriteauth45/100
Bulk creates multiple records in a Quickbase table
bulk_update_recordswriteauth45/100
Bulk updates multiple records in a Quickbase table
check_configurationread onlysource verified38/100
Check if Quickbase configuration is properly set up
configure_cacheread onlyauth35/100
Configure cache settings for the MCP server
create_appwriteauthsource verified65/100
Creates a new Quickbase application. Only use this tool when explicitly asked to create a new application.
21 of 25 tools have no visible input schema, parameter details are inferred rather than explicitly defined. Source code does not show JSON Schema definitions in tool registration for most tools.
No parameter descriptions visible in tool definitions. LLMs cannot infer what 'tableId' means or what format it should be.
create_appupdate_appget_relationships
Recommendations
Add explicit JSON Schema input definitions for all 21 tools missing them. Each parameter must include 'type', 'description', and (where applicable) 'enum', 'pattern', or 'minLength'/'maxLength'.
Expand tool descriptions to 50 - 200 chars (baseline 194). Include WHAT the tool does, WHEN to use it (vs. similar tools), and what it returns. Example: 'Creates a new Quickbase table in the specified app. Returns the new table ID for use with create_field or query_records. Only use when explicitly asked to add a new table.'
Add actionable parameter descriptions. Instead of 'The ID of the table', write 'The Quickbase table ID (a string like 'btr123abc'). Obtain via list_tables().'
Add error recovery guidance to descriptions of tools that fail on invalid input. E.g., query_records: 'If the table is not found, call list_tables() to see available tables. If the field name is invalid, call get_table_fields().'
Implement per-tool error handling that categorizes errors (retryable vs. user-fixable vs. fatal) and returns actionable messages. E.g., 'Field "status" not found in table. Available fields: [id, name, status_code, created_date].'
Add structured tool annotations to the MCP server registration: readOnlyHint=true for query_records, get_field, list_tables; destructiveHint=true for delete_field, delete_relationship; idempotentHint=true for create_app with unique name constraint.
Document output schemas for list_tables, query_records, and get_relationships. Specify field types (string, number, date, array) and include example responses. LLMs need to know the structure before planning downstream calls.
Spec posture evidence
Inferred effective spec: <=2025-11-25.
Relies on Logging (deprecated) - log to stderr or use OpenTelemetry
Score history
Overall score trend
↑ 21 points across a rubric change (v1 → v2)
32/100
Scored
Grade
Overall
Spec posture
Rubric
2026-09-22
F
32
<=2025-11-25
v2
2026-03-09
F
11
-
v1
auth
43/100
Create a relationship between two Quickbase tables
create_tablewriteauth43/100
Creates a new table in a Quickbase application
delete_fielddestructiveauth42/100
Deletes a field from a Quickbase table
delete_relationshipdestructiveauth42/100
Delete a relationship from Quickbase
download_fileread onlyauth43/100
Download a file from Quickbase
get_fieldread onlyauth45/100
Get details of a specific field in a Quickbase table
get_relationshipsread onlyauth50/100
Get relationships for a Quickbase table
get_table_fieldsread onlyauth45/100
Get all fields from a Quickbase table
list_tablesread onlyauth43/100
List all tables in a Quickbase application
query_recordsread onlyauth45/100
Query records from a Quickbase table
run_reportread onlyauth47/100
Run a report in Quickbase and retrieve the results
No error handling guidance in tool descriptions. When a tool fails (e.g., 'table not found'), there is no recovery message telling the LLM what to do next (e.g., 'Try list_tables() to see available tables'). Per pattern:recovery-guide, errors must guide recovery.
Tool descriptions are too generic or brief (under 50 chars for many tools). 'Updates a Quickbase table' does not explain WHEN to use it, what it modifies, or what the result is.
No tool annotations visible (readOnlyHint, destructiveHint, idempotentHint). Tools are marked with Risk classifications (WRITE, DESTRUCTIVE) in metadata, but these are not exposed as structured tool annotations in the MCP schema. Per current spec, these should be included.
No pagination support visible in query_records or list_tables. Large result sets risk context window exhaustion. Per pattern:paginated-result, tools returning lists must accept limit/offset and return counts.
check_configuration, test_connection, and configure_cache have empty {} input schemas, making them indistinguishable and hard for LLMs to reason about.
check_configurationtest_connectionconfigure_cache
Add pagination to list_tables, get_table_fields, query_records, and get_relationships. Include 'limit' (default 20, max 100), 'offset' (default 0), and 'totalCount' in responses. Per pattern:paginated-result, this prevents context window exhaustion.
Review composition: ensure tools do not combine multiple concerns (e.g., create_record should not also send a notification). If bulk_create_records returns only a count, add per-record success/failure details so agents can retry failed items.
Add constraints to numeric parameters (e.g., limit 1 - 100, page_size 10 - 1000). Use JSON Schema minLength/maxLength/pattern for string IDs. Per pattern:constrained-input, enums prevent hallucinated values.