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

flow-team-mcp

by baekbeombyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Flow project

create_project

Create a project in Flow by providing a title and author ID, and configure optional details like description, home tab, and permissions.

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": {
      "registerId": "<registerId>",
      "title": "<title>"
    },
    "name": "create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes프로젝트 제목
apiKeyNo
baseUrlNo
defaultTabNo홈 탭 설정
registerIdYes작성자ID
descriptionNo프로젝트 설명
postPermissionNo게시글 권한 정보
commentPermissionNo댓글 권한 정보

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as required permissions, side effects, idempotency, rate limits, or response details. The description only states the basic action, leaving the agent without insight into operational implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short and structurally simple, which is inherently concise. However, it under-specifies and essentially repeats the title, so it does not effectively use its brevity to convey important context. It is not as problematic as a single vague word, but it fails to add value beyond the name.

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 the tool's complexity (8 parameters, nested objects, no output schema, no annotations), the description is grossly insufficient. It does not explain what constitutes a Flow project, the significance of required fields, or any expected outcomes, leaving the agent to infer everything from the schema.

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?

The description adds no meaning to parameters. The schema covers 75% of parameters, but the description does not clarify the remaining undocumented parameters (apiKey, baseUrl) or explain how the parameter groups (e.g., postPermission, commentPermission) relate to project creation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Flow 프로젝트를 생성합니다' (Creates a Flow project) is essentially a direct restatement of the tool name and title. It does not add specific scope or distinguish itself from sibling tools beyond the obvious create action, making it tautological.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There is no mention of situations where a different project-related tool (e.g., list_projects, add_project_participants) would be more appropriate, nor any exclusions or prerequisites.

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