Skip to main content
Glama
Sign In
flow-team-mcp

flow-team-mcp

by baekbeombyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List projects by participant

list_participant_projects

List all Flow projects for a specific participant. Provide a participant ID to retrieve the projects they are currently involved in.

Instructions

특정 사용자가 참여 중인 Flow 프로젝트를 조회합니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "participantId": "<participantId>"
    },
    "name": "list_participant_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNo
baseUrlNo
participantIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates a read operation but does not disclose return format, pagination, authentication requirements, or behavior when no projects are found.

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 a single, concise sentence in Korean that immediately conveys the tool's purpose. It contains no redundant or filler content.

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?

The tool is relatively simple with 3 parameters and no output schema, and the description gives the core purpose. However, it lacks usage guidance, parameter context for apiKey/baseUrl, and any indication of the response shape, making it barely adequate.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It clarifies participantId as the 'specific user' but does not explain apiKey or baseUrl beyond what their names imply. More guidance on these parameters is needed.

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 states a specific action ('retrieves') and a specific resource ('Flow projects in which a specific user participates'). This clearly distinguishes it from sibling tools like list_projects (all projects) and get_project_participants (participants of a project).

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

Usage Guidelines3/5

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

The intended use case is implied by the description, but there is no explicit guidance on when to use this tool versus alternatives such as list_projects or get_project_participants. No exclusions or context are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools