Single tool with basic schema and minimal description. Tool name 'execute_influxql' lacks action verb clarity (should be 'query_influxql' or 'run_influxql'). Description is 54 chars, acceptable but generic. Input schema present with proper type and description for 'query' parameter. No output schema documented. No error handling guidance for LLMs. No parameter constraints (e.g., query length limits, timeout hints). Security: query validation is server-side (good), but no documentation of what queries are safe. Resources feature present but tool composition is weak, no integration between resource discovery and query execution.
Execute InfluxQL query against openGemini.
No output schema documented. LLMs cannot plan downstream operations or extract structured data from query results.
Tool name 'execute_influxql' is generic. Verb 'execute' does not clearly signal a read-only query operation. Should be 'query_influxql' or 'run_influxql_query'.
No error handling guidance. Query validation (SELECT/SHOW only, no DROP/ALTER/INSERT) is enforced server-side but LLM receives only plain-text rejection. Should return structured error with recovery hints.
Parameter 'query' lacks constraints. No mention of max length, timeout behavior, or result limits (RESULTS_LIMIT=100 is hardcoded but not documented in schema).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | <=2025-11-25 | v2 |
Resources (databases, measurements) are discoverable but not integrated with tool. No guidance on how to use resource URIs with the query tool, forcing agents to manually construct queries.