Skip to main content
Glama

add_feature

Add a new feature to the current session when additional work is discovered, with optional placement after an existing feature ID.

Instructions

Add a new feature to the current session. Use this when you discover additional work needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectDir": "<projectDir>",
      "description": "<description>"
    },
    "name": "add_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path to the project directory
descriptionYesDescription of the new feature
insertAfterNoOptional: Insert after this feature ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It implies a mutation against session state but says nothing about whether a session must already exist, whether the feature is queued or immediately routed, or what the caller gets back. The word "session" is the only hint about state dependency and is never defined.

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?

Two short sentences with no filler, and the action statement is front-loaded ahead of the usage condition. There is no redundancy or hedging to trim.

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?

This is a stateful mutation with three parameters, no annotations, and no output schema, so the description should say what the call returns and what session prerequisites apply. Instead it stops at the trigger condition, leaving the agent to guess at the result and the ordering semantics of insertAfter.

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 the baseline is 3 and the description is not required to re-explain projectDir or description. It does add the notion that the feature lands in the current session, but the meaning and ordering effect of insertAfter is left entirely to the schema.

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 states a specific verb and resource ("Add a new feature") and scopes it to "the current session", which is more than a restatement of the name. It does not distinguish itself from the closest sibling, enqueue_feature, so an agent cannot tell from the text alone which of the two to pick.

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

Usage Guidelines3/5

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

"Use this when you discover additional work needed" gives a usable trigger condition, which is real when-to-use guidance. It offers no when-not guidance and names no alternative path (e.g. enqueue_feature or route_feature), leaving the choice between siblings to inference.

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