Loading ToolBench

Reading the current corpus…

software-engineer-agent MCP server · F · ToolBench

software-engineer-agent

github.com/afernandezde/software-engineer-agent

A Spring Boot-based AI agent that uses MCP tools to assist with software engineering tasks, including ticket resolution, code modification, and GitHub integration. Routes user intents to specialized workflows and integrates with LLMs via Spring AI.

2026-07-28+STREAMABLE_HTTP4 tools

34/100

Definition Quality36

Protocol Readiness35

Supportability30

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: Streamable HTTP

Current-spec patterns detected

Summary

This server has severe definition quality issues. Tool descriptions are minimal or in Spanish without English translations. Input schemas are partially visible but lack proper type definitions and parameter descriptions. The safeGithubPush tool has a Spanish description ('ÚSALA SIEMPRE...') that is non-standard for production MCP. Two tools (jira_issues, read_file) have no visible input schemas in the provided code. Output schemas are not documented. Error handling is minimal. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present despite two tools being WRITE operations. The server appears to be a proof-of-concept rather than production-grade.

Tools (4)

jira_issuesread onlyauthsource verified27/100

Retrieves Jira issues for ticket resolution workflows

push_fileswriteauthsource verified48/100

MCP tool for pushing files to GitHub repositories

read_fileread onlysource verified30/100

Reads file contents from the local filesystem

safeGithubPushwriteauthsource verified37/100

ÚSALA SIEMPRE PARA SUBIR ARCHIVOS A GITHUB. Lee el archivo local y lo sube.

Issues (5)

CRITICALtool-description ↗

Two tools (jira_issues, read_file) have no visible input schemas in source code.

jira_issuesread_file

CRITICALtool-description ↗

Tool descriptions are inadequate. safeGithubPush uses Spanish ('ÚSALA SIEMPRE PARA SUBIR ARCHIVOS A GITHUB') instead of English. jira_issues and read_file have generic 20-char descriptions.

safeGithubPushjira_issuesread_file

HIGHtool-annotations ↗

No tool annotations present. safeGithubPush and push_files are WRITE operations that should declare destructiveHint=true. read_file should declare readOnlyHint=true. Missing annotations prevent LLMs from understanding operation safety.

safeGithubPushpush_filesread_file

HIGHconstrained-input ↗

Parameter descriptions are minimal or missing. safeGithubPush parameters have basic descriptions but lack format constraints (e.g., 'filePath' should specify absolute path format). No enum constraints or validation guidance.

Recommendations

Provide complete input schemas for jira_issues and read_file with explicit type definitions and parameter descriptions.
Rewrite all tool descriptions in English, 50-200 characters, following pattern: 'WHAT it does, WHEN to use it, WHAT it returns.' Example: 'Pushes one or more files to a GitHub repository branch. Use after modifying local files. Returns commit SHA and GitHub URL.'
Add tool annotations: destructiveHint=true for safeGithubPush and push_files; readOnlyHint=true for read_file and jira_issues.
Document output schemas for all tools. Example for push_files: '{commit_sha: string, github_url: string, files_pushed: number}'
Add parameter constraints: filePath should specify 'absolute path format (e.g., /home/user/file.java or C:\Users\file.java)'; branch should default to 'main' or 'master'; message should have min 10 chars.

Score history

Overall score trend

First recorded score · v2 rubric

34/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	34	2026-07-28+	v2