Loading ToolBench
Servidor MCP local, somente leitura, que expõe um repositório a agentes de IA sem expor os dados que vivem dentro dele
Three tools with Portuguese descriptions and basic schemas. All tools are read-only and properly annotated with ToolAnnotations. However, descriptions lack LLM-optimized structure (no WHAT/WHEN/HOW guidance), parameter descriptions are minimal or absent, and output schemas are not documented. list_files has the most complete schema with typed parameters and descriptions; project_overview and get_project_state have empty input schemas. Error handling exists (ToolError with Portuguese messages) but lacks recovery guidance. No parameter validation constraints (enums, ranges) visible. Average tool score: 58.
Resumo do estado persistente conhecido (índice), sem tocar no disco.
Lista um diretório, com tamanho e marcação de conteúdo bloqueado. Paginado: reenvie o `next_cursor` recebido em `start_after` para continuar. Entradas com `bloqueado` existem no disco mas não têm o conteúdo servido — "privado" é zona de dados pessoais, "ignorado" é pasta gerada.
Conta arquivos e diretórios visíveis do workspace, ao vivo. Varre o disco: para a visão barata (vinda do índice), use get_project_state.
project_overview and get_project_state have empty input schemas ({}).
Descriptions lack LLM-optimized structure. Missing explicit WHAT/WHEN/HOW guidance. E.g., project_overview says 'Conta arquivos...' but does not state when to use it vs get_project_state, or what the output structure is. Baseline: 50-200 chars with clear intent.
Output schemas not documented. LLMs cannot plan downstream calls or extract fields. E.g., list_files returns JSON with 'bloqueado', 'next_cursor', etc., but no schema is visible in the tool definition.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 53 | <=2025-11-25 | v2 |
Error messages are in Portuguese and lack recovery guidance. E.g., 'Caminho não encontrado' tells the LLM the path is missing but not what to do next (e.g., 'Call list_files on the parent directory'). Per pattern:recovery-guide, errors must guide the next action.
No parameter constraints (enums, ranges, patterns) visible. E.g., 'limit' defaults to 200 but no min/max bounds stated. 'relative_path' accepts any string with no validation hints. Per pattern:constrained-input, enums and ranges prevent hallucinated values.