Skip to main content
Glama

list_team_intents

List intents from team members in a repository to view ongoing work, identify overlaps, and review statuses.

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.
Behavior3/5

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

With no annotations, the description carries full burden. It explains server-side filtering and pagination (default 50 per page, limit/offset, count meaning). However, it does not state that the operation is read-only or mention auth/rate limits.

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?

The description is well-structured: a short introductory sentence, bullet points for use cases, then a concise paragraph on filtering/pagination. It is front-loaded and avoids fluff.

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

Completeness3/5

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

Given 10 parameters and no output schema, the description covers basic behavior and pagination but lacks details on return format or how to interpret results. Parameters like forkAuthor and workspaceId are mentioned but not fully explained.

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 is 3. The description adds context about server-side filtering and pagination behavior for limit/offset/count, but does not significantly enhance individual parameter meanings beyond the 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?

The description clearly states 'List intents from team members for this repository' with a specific verb and resource. It distinguishes from siblings by focusing on team-wide listing, while other tools deal with creation, activation, or file-specific 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 explicitly lists use cases: 'See what your team is working on', 'Check for potential overlapping work', 'Review the status'. It provides clear context but does not explicitly mention when not to use it or alternatives.

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