Skip to main content
Glama

update_intent

Update an active intent's title, description, scope, or constraints as understanding evolves during work, ensuring intents reflect actual work rather than initial guesses.

Instructions

Update an active intent's title, description, scope, or constraints.

Use this to reformulate an intent as understanding evolves during work. Intents are living documents — they should be updated to reflect what the work actually became, not left as the initial guess. Common triggers for reformulation:

  • The real problem turned out to be different from the initial hypothesis

  • Scope expanded or narrowed during investigation

  • The approach changed after discovering constraints

If no intentId is provided, the currently active intent is updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoUpdated scope for the intent
titleNoUpdated title for the intent
intentIdNoID of the intent to update. If omitted, updates the currently active intent.
repoPathYesLocal path to the repository root
forkAuthorNoFork attribution; usually resolved by Muninn automatically — pass only for override / testing.
repoOriginNoGit remote origin URL. Auto-detected from repoPath via git if not provided.
constraintsNoUpdated constraints for this work
descriptionNoUpdated description for the intent
workspaceIdNoWorkspace identifier; usually resolved by Muninn automatically — pass only for override / testing.
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like mutation, merging behavior, return value, and permissions. It only states 'update' without detailing whether fields are overwritten or merged, or what the response looks like.

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 concise with two front-loaded paragraphs. The first sentence captures the action and fields, and the examples are relevant. No redundant text.

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?

Given 9 parameters, nested objects, and no output schema, the description lacks details on return values, error handling, and update semantics. It does not fully compensate for the missing output 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?

Schema coverage is 100%, so baseline 3. The description adds minimal extra semantics beyond the schema, mainly repeating the fields and the default behavior for intentId. The rationale for updating is helpful but not parameter-specific.

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 clearly states the tool updates an active intent's title, description, scope, or constraints. It distinguishes itself from sibling tools like create_and_activate_intent and activate_intent by emphasizing reformulation of existing intents.

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?

The description provides explicit triggers for reformulation and notes that omitting intentId updates the active intent. However, it does not explicitly state when not to use this tool, such as for creating or activating intents.

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

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