Skip to main content
Glama

list_team_intents

List team intents for a repository to see ongoing work, detect overlapping tasks, and review feature status. Supports filtering by status, author, date, and pagination.

Instructions

List intents from team members for this repository.

Use this to:

  • See what your team is working on

  • Check for potential overlapping work before starting a new task

  • Review the status of various features/refactors in progress

Filtering (status, author, date range) and pagination are applied server-side across the full result set (default: 50 per page; use limit/offset to page). count is the total number of matching intents, not just the returned page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of intents to return (default: 50)
sinceNoFilter intents updated after this ISO8601 date (e.g. "2026-04-01")
untilNoFilter intents updated before this ISO8601 date
authorNoFilter by author name or ID
offsetNoNumber of intents to skip for pagination (default: 0)
statusNoFilter by intent status.
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.
Behavior4/5

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

With no annotations provided, the description carries full behavioral disclosure. It explains server-side filtering and pagination (default 50 per page), the meaning of the 'count' field, and that parameters like forkAuthor are auto-resolved. While it doesn't describe all behaviors (e.g., ordering), it adds significant context beyond the schema.

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 and front-loaded with the main purpose, followed by bullet points for use cases and key behavioral details. Every sentence adds value with no redundancy.

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?

Given the complexity (10 parameters, no output schema), the description adequately covers the tool's functionality, filtering, pagination, and the meaning of the count field. It does not describe the full output structure but is sufficient for an AI agent to use the tool effectively.

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% with good parameter descriptions. The description adds extra value by specifying the default limit value (50), the ISO8601 format for date filters, and noting that forkAuthor and workspaceId are auto-resolved. This goes beyond the schema's information.

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 'List intents from team members for this repository' with specific use cases like checking overlapping work and reviewing status. It distinguishes itself from siblings by focusing on team-wide intents, not file-specific or intent-specific actions.

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 explicitly states when to use the tool with three bullet-point scenarios. However, it does not mention when not to use it or direct users to alternative sibling tools like get_intents_for_file or get_intents_for_lines, which would be helpful.

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