FastMCP server providing Looker data access via Google GenAI Toolbox with 15 prebuilt Looker tools
Critical gaps across all dimensions. Tool definitions are inferred from file references rather than explicitly visible in source code. No input schemas are visible in the provided code. Descriptions are minimal (6-25 chars), far below the 50-200 char baseline for LLM-optimized tools. No parameter documentation. No output schemas documented. The server.py file is referenced but not provided, making it impossible to verify actual tool registration, schema definitions, or parameter handling. Based on visible evidence only: tools appear to be defined but schemas and detailed descriptions are not shown.
Get Looker dimensions
Get Looker explores
Get Looker filters
Get Looker looks
Get Looker measures
Get Looker models
Get Looker parameters
Create a Looker look
No input schemas visible for any tool. Cannot verify parameter types, constraints, or validation.
Descriptions are 6-25 characters, far below 50-200 char baseline. Examples: 'Get Looker models' (17 chars), 'Execute a Looker query' (22 chars). Descriptions do not explain WHEN to use each tool or what distinguishes similar tools (e.g., query vs query_sql vs query_url).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 28 | 2026-07-28+ | v2 |
Execute a Looker query
Execute a SQL query in Looker
Get Looker query URL
Run a Looker look
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields. No indication of pagination support, field structure, or chaining IDs (e.g., does get_explores return explore_id for use in query?).
Tool definitions inferred from file references only. Actual server.py code not provided. Cannot verify registration, parameter handling, or error handling.
No error handling guidance visible. No indication of retryable vs fatal errors, no recovery suggestions, no validation error messages. Agents will have no guidance on what to do if a query fails or a look is not found.