Skip to main content
Glama

activate_intent

Set an existing intent as your current focus by its ID. Use it to switch intent focus, reactivate a deactivated intent, or resume an abandoned one with restored decisions.

Instructions

Activate an existing intent by ID — sets it as THIS session's current focus.

Use this to:

  • Switch your current focus to a different intent found via list_team_intents or get_relevant_context

  • Re-activate an intent that was deactivated (e.g., to complete it)

  • Resume work on a previously created intent

  • Resume an "abandoned" intent (see below)

Accepts both cloud IDs (from get_relevant_context / API) and local UUIDs (from list_team_intents).

Multi-active model: activating an intent only moves YOUR session's current pointer. Many intents can be active on a repo at once (one current per session/teammate), so this never blocks on or displaces another session's active intent — there is no lock to take over.

Resuming abandoned intents:

  • Abandoned intents have their decisions soft-deleted (invisible to recall and get_relevant_context). Activating one transparently restores them — single-intent decisions for this intent get their soft-delete cleared so the prior reasoning becomes visible again. Multi-intent decisions stay visible throughout (they were never soft-deleted).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentIdYesThe cloud ID (preferred) or local UUID of the existing intent to activate.
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.
workspaceIdNoWorkspace identifier; usually resolved by Muninn automatically — pass only for override / testing.
Behavior5/5

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

No annotations provided, so description carries full burden. Thoroughly explains the multi-active model (no lock, per-session pointer), restoration of soft-deleted decisions for abandoned intents, and acceptance of both cloud IDs and local UUIDs. Also notes automatic resolution of certain parameters.

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?

Description is well-structured with sections and bullet points, front-loaded with main purpose. Every sentence adds value, though slightly longer than necessary. Still efficient for the complexity.

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

Completeness4/5

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

For a tool with 5 parameters, nested objects, and no output schema, the description covers behavior comprehensively: multi-active model, decision restoration, accepted IDs. Missing output behavior, but overall complete enough for effective use.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds value by explaining the difference between cloud ID and local UUID for intentId, and that forkAuthor and workspaceId are usually auto-resolved. Provides context on repoOrigin auto-detection, going beyond schema.

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?

Clearly states the verb 'Activate' and the resource 'existing intent by ID', specifying it sets the intent as the current session's focus. Distinguishes from sibling tools like 'create_and_activate_intent' and 'list_team_intents' by listing specific use cases.

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

Usage Guidelines5/5

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

Explicitly lists when to use the tool: switching focus, re-activating deactivated intents, resuming work, and resuming abandoned intents. Implicitly excludes creation (handled by sibling) and provides context for when not to use.

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