Skip to main content
Glama

update_features

Add unassigned intents to the feature catalog additively, preserving existing features. Refresh the project's high-level purpose view from recorded intents.

Instructions

Update the project's feature catalog from its recorded intents.

Additively groups any intents that are not yet assigned to a feature into the running catalog (an incremental "extend"), without disturbing existing features. The feature catalog is the high-level "what does this project actually do?" view, derived from the repo's intents.

When to use:

  • After recording or completing intents, to keep the feature list current.

  • On demand, when you want the catalog refreshed with recent work.

Behavior:

  • Additive only — never deletes or re-derives existing features.

  • Intents already assigned to a feature are skipped; only unassigned ones are processed.

  • Runs in the Kawa Code desktop app and returns the resulting feature count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoPathYesLocal path to the repository root
Behavior4/5

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

With no annotations, description covers key behavioral traits: additive only, skips already assigned intents, runs in Kawa Code desktop app, returns feature count. Could mention reversibility or permissions but sufficient.

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?

Description is concise and well-structured: purpose first, then usage, then behavior bullets. No wasted words, every sentence adds value.

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

Completeness5/5

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

Given one parameter and no output schema, description provides all needed information: what it does, when to use, behavioral details, and return value. Complete.

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?

Only parameter repoPath has full schema coverage. Description does not add extra meaning beyond schema's 'Local path to the repository root'. Baseline of 3 is appropriate.

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?

Description clearly states it updates the project's feature catalog from recorded intents. It specifies the additive nature and contrasts with other tools by focusing on feature catalog updates.

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

Usage Guidelines4/5

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

Provides explicit 'When to use' section with two specific scenarios. Lacks explicit when-not-to-use or alternative tools, but context is clear enough.

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/kawacode-ai/kawa.mcp'

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