Loading ToolBench

Reading the current corpus…

ticketron MCP server · F · ToolBench

ticketron

A CLI application for creating JIRA tickets using LLM-powered ticket generation with MCP (Model Context Protocol) integration

2026-07-28+8 tools

31/100

Definition Quality41

Protocol Readiness5

Supportability33

Spec posture

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

Static source inference · medium confidence

Current-spec patterns detected

Summary

Ticketron is a CLI tool with 8 commands, but lacks MCP protocol implementation. Tool definitions are inferred from Cobra command structure rather than explicit MCP registration. Only 1 of 8 tools has visible input schema (config set-key). Descriptions exist but are brief (avg ~80 chars, below 194-char baseline). No output schemas documented. No error handling guidance. No tool annotations. The 'create' tool is complex (6 params) but lacks parameter descriptions for most fields. This is a CLI wrapper, not an MCP server.

Tools (8)

config initwrite47/100

Creates the default configuration directory and files if they don't exist. This command ensures that the necessary configuration structure is in place for Ticketron to function correctly.

config locateread only45/100

Displays the paths to the configuration files being used by Ticketron. This command helps you find where Ticketron is looking for its settings.

config set-keywriteauth50/100

Stores the OpenAI API key securely in the operating system's keychain or keyring. This is the recommended way to configure the API key for Ticketron. The key will be associated with the service 'ticketron' and user 'openai_api_key'.

config showread only43/100

Displays the currently loaded configuration values from config files and environment variables.

context addwrite50/100

Add a new entry (line) to the context file

context editwrite42/100

Edit the context file using $EDITOR

context showread only42/100

Show the content of the context file

create

Issues (5)

CRITICALtool ↗

No MCP protocol implementation detected. This is a Cobra CLI tool, not an MCP server. Tool definitions are inferred from command structure, not explicit MCP tool registration.

config initconfig locateconfig set-keyconfig showcontext showcontext editcontext addcreate

CRITICALconstrained-input ↗

7 of 8 tools have no visible input schema. Only 'config set-key' and 'context add' show parameter definitions. Remaining tools (config init, config locate, config show, context show, context edit, create) lack documented input schemas.

config initconfig locateconfig showcontext showcontext editcreate

HIGHtool-description ↗

'create' tool has 6 parameters but only 'summary' has a description. Parameters 'type', 'project', 'description', 'interactive', 'output' lack descriptions explaining their purpose, constraints, or valid values.

create

Recommendations

Implement MCP protocol: wrap Cobra commands as MCP tools with explicit tool registration, input schemas, and output schemas. Use the MCP Go SDK or implement the JSON-RPC protocol directly.
Add complete input schemas for all 8 tools. For 'create', document all 6 parameters: type (enum: Bug|Task|Story|etc), project (string, format), description (string, max length), interactive (boolean, default false), output (enum: json|text, default text).
Document output schemas for each tool. E.g., 'config show' should return {config: {openai_api_key: string, jira_url: string, ...}}. 'create' should return {ticket_id: string, url: string, summary: string}.
Add error handling guidance. E.g., 'config set-key' should document: 'Error: keyring unavailable on this system. Fallback: set TICKETRON_OPENAI_API_KEY environment variable.' 'create' should document: 'Error: JIRA authentication failed. Verify project key and API credentials.'
Add tool annotations (destructiveHint, readOnlyHint, idempotentHint) to guide agent behavior. Mark 'config set-key', 'context edit', 'context add', 'create' as destructive. Mark 'config locate', 'config show', 'context show' as readOnly.

Score history

Overall score trend

First recorded score · v2 rubric

31/100

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