Skip to main content
Glama

create_feature

Create a feature in Aha! by specifying release and name, with optional details for scheduling, estimation, assignment, and workflow.

Instructions

Create a new feature in Aha!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
epicNoName or ID of epic
nameYesName of the feature (required)
tagsNoTags to add to the feature (comma-separated)
teamNoNumeric ID or key of the team
due_dateNoDate that work is due to be completed (YYYY-MM-DD format)
created_byNoEmail address of the user who created the feature
initiativeNoName or ID of initiative
release_idYesNumeric ID or key of the release (required)
start_dateNoDate that work will start (YYYY-MM-DD format)
descriptionNoDescription of the feature (may include HTML formatting)
release_phaseNoName or ID of release phase
workflow_kindNoType of feature
workflow_statusNoStatus of the feature
assigned_to_userNoUser assigned to the feature
initial_estimate_textNoInitial estimated effort (e.g., '2d 1h' for time or '4p' for points)
detailed_estimate_textNoDetailed estimated effort (e.g., '2d 1h' for time or '4p' for points)
remaining_estimate_textNoRemaining estimated effort (e.g., '2d 1h' for time or '4p' for points)
Behavior2/5

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

With no annotations, the description carries full burden but only states 'Create a new feature in Aha!'. It discloses that this is a write operation, but nothing about required inputs, potential side effects, or return behavior. Since there is no output schema, this is inadequate.

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

Conciseness5/5

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

The description is a single, front-loaded sentence. It is minimal but not padded, achieving maximum brevity and clarity. Every word earns its place.

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

Completeness1/5

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

For a tool with 17 parameters and no output schema, this one-sentence description provides almost no contextual completeness. It does not explain what a feature is, how it relates to a release, or what the tool returns. The agent is left to infer everything from the schema.

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?

All 17 parameters are fully described in the input schema, so the description's lack of parameter detail is acceptable. The schema provides definitions for each field, including required ones, meeting the baseline for high schema coverage.

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

Purpose5/5

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

The description uses the specific verb 'Create' and names the resource 'feature' within 'Aha!', clearly distinguishing it from sibling read/search tools. The purpose is unambiguous and immediately understood.

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 is provided on when to use this tool versus alternatives, nor any prerequisites like needing a release_id. The description is a bare statement with zero usage context, leaving the agent to infer when this tool should be invoked.

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/popand/aha-mcp'

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