Skip to main content
Glama

agent

Manages active agent workflow actions including intake, planning, verification, and release, with Jira ticket creation from strict templates.

Instructions

Active agent workflow actions: intake/plan/verify/release plus Jira ticket creation from strict MAIN DESCRIPTION templates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoProject path (default: current directory)
briefNoStructured or plain brief text for planning
actionNoActive workflow action
labelsNoOptional labels to set when creating Jira tickets
ticketNoTicket key for intake/plan actions (e.g. PROJ-123)
summaryNoOptional Jira summary (defaults to first line of MAIN DESCRIPTION)
versionNoTarget release version for release action (e.g. v1.2.0)
createTagNoIf true, release action creates annotated git tag when CI is green
issueTypeNoOptional Jira issue type override (Task/Story/Bug)
projectKeyNoOptional Jira project key override
prototypeViewNoPROTOTYPES section value: View
originKeyLogicNoORIGIN section value: Key Logic
originOldQueryNoORIGIN section value: Old Query
prototypePropsNoPROTOTYPES section value: Props
destinationViewNoDESTINATION section value: View
mainDescriptionNoMAIN DESCRIPTION body used to create Jira tickets
originComponentNoORIGIN section value: Component
destinationModelNoDESTINATION section value: Model
destinationRouteNoDESTINATION section value: Route
createPullRequestNoIf true, release action opens PR/MR when provider is configured
acceptanceCriteriaNoAcceptance criteria list for strict Jira template
dataTransformationNoDATA TRANSFORMATION section content
createFromDescriptionNoWhen action is intake, create Jira ticket first from MAIN DESCRIPTION template
destinationControllerNoDESTINATION section value: Controller
prototypeRelatedFilesNoPROTOTYPES related files list
prototypeDesignPatternNoPROTOTYPES section value: Design Pattern
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose behavioral traits such as whether actions are destructive, require authentication, or have side effects (e.g., creating tickets or tags).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the core purpose. It is efficient but could be structured more clearly with bullet points for actions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 26 parameters and no output schema, the description is too brief. It omits explanation of the workflow lifecycle, how actions interrelate, and the meaning of 'strict MAIN DESCRIPTION templates', leaving significant gaps for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema—it highlights the MAIN DESCRIPTION template but does not explain parameter relationships or usage context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool handles agent workflow actions (intake/plan/verify/release) and Jira ticket creation from MAIN DESCRIPTION templates. It distinguishes from sibling tools like setup or rules by focusing on workflow actions, but the verb 'active' is somewhat vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. It lists actions but does not explain the conditions for choosing one action over another, nor does it mention prerequisites or when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/isucorp-taimiralain/StackGuide-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server