MCP Server extension for Laravel Telescope
Laravel Telescope MCP demonstrates solid definition quality with consistent naming conventions, complete parameter schemas, and clear descriptions across all 8 tools. All tools follow verb_noun naming patterns (batches, cache, commands, dumps, events, exceptions, gates, http-client). Schemas are well-structured with proper JSON Schema types, enums, and descriptions. However, there are gaps in output schema documentation, error handling guidance, and some parameter descriptions lack action-oriented detail. The server excels at parameter validation constraints (enums, limits, filters) but falls short on recovery guidance and return value documentation.
Lists and analyzes batch operations recorded by Telescope.
Lists and analyzes cache operations recorded by Telescope.
Lists and analyzes command executions recorded by Telescope.
Lists and analyzes dump entries recorded by Telescope.
Lists and analyzes events recorded by Telescope.
Displays exceptions recorded by Telescope, allowing you to view complete details of application errors.
Lists and analyzes gate authorization checks recorded by Telescope.
Output schemas not documented. Tools return formatted text output but LLMs cannot parse response structure to extract fields for downstream calls. For example, batches returns a formatted ASCII table rather than structured JSON fields (id, name, status, total, finished, pending, failed, created_at). This breaks tool chaining.
Error handling lacks recovery guidance. Code catches exceptions and returns Response::error() with only the exception message (e.g., 'Error: <message>'). Does not classify errors as retryable, user-fixable, or fatal. Does not suggest alternative tools or next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 66 | 2026-07-28+ | v2 |
Lists and analyzes HTTP requests made by Laravel HTTP client.
Generic tool name 'gates' lacks action verb. Should be 'list_gates' or 'check_gates' to make intent clear. Current name is ambiguous, does it retrieve gates, authorize against gates, or modify gates?
Parameter descriptions for filter parameters lack context on partial matching behavior. For example, 'cache' tool's 'key' parameter says 'Filter by cache key (partial match)' but other tools do not clarify whether string filters are exact, case-sensitive, or substring. This invites LLM misuse.
'dumps' tool description is vague: 'Lists and analyzes dump entries recorded by Telescope.' Does not explain what 'dump entries' are, when to use this tool, or what 'analyzed' means. Baseline descriptions should be 50-200 chars and answer WHAT, WHEN, and WHAT-RETURNS.