Single tool 'loki_query' has a complete input schema with 8 parameters, all typed and described. Tool description is adequate (58 chars) but minimal. Parameter descriptions are present and reasonably detailed (e.g., 'LogQL query string', 'Loki server URL (default: http://localhost:3100 from LOKI_URL env var)'). However, output schema is not documented, the tool returns unstructured log results but the response format is not formally specified. No error handling guidance provided. Tool naming follows verb_noun pattern (loki_query) but is somewhat generic; 'query_loki_logs' would be more action-oriented. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present despite being READ_ONLY. Missing guidance on when to use this tool vs. alternatives, and no pagination/limit enforcement documented in the description.

• Expand tool description to 150 - 250 chars. Include: what it does, when to use it, what it returns. Example: 'Query Grafana Loki for logs matching a LogQL expression. Returns matching log entries with timestamps and labels. Use to search logs by job, service, or custom label filters. Supports time range filtering and result limits.'
• Document the output schema explicitly. Specify: response is an array of log entries, each with {timestamp: string (ISO 8601), labels: object, message: string}. Include pagination info if applicable (total_entries, has_more).
• Add error handling guidance to the tool description or implementation. Return structured errors like: {isError: true, content: [{type: 'text', text: 'Loki server unreachable at http://localhost:3100. Check LOKI_URL env var and network connectivity.'}]}
• Remove username/password/token from tool parameters. Inject credentials server-side via LOKI_USERNAME, LOKI_PASSWORD, LOKI_TOKEN env vars only. Document this in the server README.
• Add readOnlyHint=true annotation to the tool definition to signal to agents that this tool is safe to retry and has no side effects.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry