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

flow-team-mcp

by baekbeombyeon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Flow project columns

get_project_columns

Retrieves the list of columns for a specified Flow project using the project ID and user ID. Provides column details to support project management and workflow organization.

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": {
      "projectId": "<projectId>",
      "userId": "<userId>"
    },
    "name": "get_project_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNo
userIdYes프로젝트 컬럼 조회 기준 사용자 ID
baseUrlNo
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits on its own. It only states that the tool retrieves columns, giving no information about return format, pagination, error behavior, or authorization requirements. This is insufficient for the agent to understand side effects or data semantics.

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 a single concise sentence that efficiently states the tool's core action and resource. It is front-loaded with the action and contains no redundant words, though it is so brief that it borders on under-specification.

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?

The tool has four parameters and no output schema, so the description should provide extra context about what the returned column list looks like and how it relates to status columns. The current one-liner offers no guidance on response structure or when to use this over related tools, making it incomplete for an agent to invoke confidently.

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 schema provides descriptions only for userId ('프로젝트 컬럼 조회 기준 사용자 ID'), while projectId, apiKey, and baseUrl have no description. The tool description adds no parameter-specific meaning beyond the schema, and with only 25% schema coverage, it fails to compensate for the lack of documentation on the remaining parameters.

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

Purpose4/5

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

The description clearly states the tool retrieves the column list of a Flow project using the verb '조회합니다' (retrieve) and the resource 'Flow 프로젝트 컬럼' (Flow project columns). However, it does not explicitly distinguish this from the sibling tool get_project_status_columns, which likely returns status columns specifically, leaving some ambiguity about scope.

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?

There is no guidance on when to use this tool versus alternatives such as get_project_status_columns or list_projects. The description lacks any mention of prerequisites, context, or exclusions, leaving the agent to infer usage solely from the tool name.

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