Skip to main content
Glama
re171113-byte

Startup Helper MCP

get_business_trends

Analyze recent startup trends and industry growth/decline patterns to identify emerging business opportunities and sector performance.

Instructions

최근 창업 트렌드와 업종별 성장/쇠퇴 현황을 분석합니다. 어떤 업종이 뜨고 있는지 알려드립니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNo지역 (선택, 예: 서울, 부산, 전국)
categoryNo관심 업종 카테고리 (선택)
periodNo분석 기간, 기본값: 6개월6months

Implementation Reference

  • The core handler function implementing the get_business_trends tool logic. It processes inputs to generate business trends data including rising/declining sectors, insights, and recommendations using predefined data sources.
    export async function getBusinessTrends(
      region?: string,
      category?: string,
      _period?: "3months" | "6months" | "1year"
    ): Promise<ApiResult<BusinessTrends>> {
      try {
        // 지역별 인사이트 추가
        let insights = [...TREND_DATA.insights];
        if (region) {
          const normalizedRegion = Object.keys(REGIONAL_TRENDS).find((r) =>
            region.includes(r)
          );
          if (normalizedRegion) {
            insights = [
              ...REGIONAL_TRENDS[normalizedRegion].map((t) => `[${normalizedRegion}] ${t}`),
              ...insights,
            ];
          }
        }
    
        // 추천 메시지 생성
        const recommendation = generateRecommendation(region, category);
    
        return {
          success: true,
          data: {
            period: TREND_DATA.period,
            region: region || "전국",
            rising: TREND_DATA.rising,
            declining: TREND_DATA.declining,
            insights,
            recommendation,
          },
          meta: {
            source: "소상공인시장진흥공단 통계",
            timestamp: new Date().toISOString(),
          },
        };
      } catch (error) {
        console.error("트렌드 조회 실패:", error);
    
        return {
          success: false,
          error: {
            code: "TREND_FAILED",
            message: "트렌드 정보 조회 중 오류가 발생했습니다.",
            suggestion: "잠시 후 다시 시도해주세요.",
          },
        };
      }
    }
  • TypeScript interfaces defining the output structure for BusinessTrends and TrendingBusiness used by the tool.
    export interface TrendingBusiness {
      name: string;
      growthRate: number;
      count: number;
    }
    
    // 창업 트렌드 결과
    export interface BusinessTrends {
      period: string;
      region: string;
      rising: TrendingBusiness[];
      declining: TrendingBusiness[];
      insights: string[];
      recommendation: string;
    }
  • src/index.ts:107-126 (registration)
    MCP server registration of the 'get_business_trends' tool, including name, description, Zod input schema, and wrapper handler that calls the core implementation.
    server.tool(
      "get_business_trends",
      "최근 창업 트렌드와 업종별 성장/쇠퇴 현황을 분석합니다. 어떤 업종이 뜨고 있는지 알려드립니다.",
      {
        region: z.string().optional().describe("지역 (선택, 예: 서울, 부산, 전국)"),
        category: z.string().optional().describe("관심 업종 카테고리 (선택)"),
        period: z
          .enum(["3months", "6months", "1year"])
          .optional()
          .default("6months")
          .describe("분석 기간, 기본값: 6개월"),
      },
      async ({ region, category, period }) => {
        const result = await getBusinessTrends(region, category, period);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
          isError: !result.success,
        };
      }
    );
  • Helper function to generate personalized recommendations based on category input, used within the main handler.
    function generateRecommendation(
      region?: string,
      category?: string
    ): string {
      if (category) {
        const rising = TREND_DATA.rising.find((t) => t.name.includes(category));
        const declining = TREND_DATA.declining.find((t) => t.name.includes(category));
    
        if (rising) {
          return `${category} 업종은 현재 성장세(+${rising.growthRate}%)입니다. 시장 진입에 좋은 시기입니다.`;
        }
        if (declining) {
          return `${category} 업종은 현재 하락세(${declining.growthRate}%)입니다. 진입 시 차별화 전략이 필수입니다.`;
        }
      }
    
      return "무인매장, 반려동물 서비스, 건강식 등 성장 업종을 고려해보세요. 일반 커피전문점, 치킨은 포화 상태입니다.";
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions analyzing trends but lacks behavioral details such as data sources, update frequency, rate limits, authentication requirements, or what the output looks like (e.g., structured data vs. summary). This is a significant gap for a tool with no annotations.

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 concise and front-loaded, consisting of two sentences that directly state the tool's purpose. There is no wasted text, and it efficiently communicates the core function. However, it could be slightly more structured by explicitly listing key features.

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 complexity (3 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits, output format, and usage guidelines. For a tool that analyzes business trends, more context on data freshness, scope, and limitations is needed to be fully helpful.

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?

The schema description coverage is 100%, so the schema already documents all parameters (region, category, period) with descriptions and enums. The description adds no additional parameter semantics beyond what's in the schema, such as examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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's purpose: analyzing recent startup trends and industry growth/decline status. It specifies the verb 'analyzes' and resource 'business trends/industries', making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'analyze_commercial_area' or 'find_competitors', which might also involve business analysis.

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. It mentions what it does but doesn't specify contexts, prerequisites, or exclusions. For example, it doesn't clarify if this is for high-level trend analysis compared to more detailed tools like 'analyze_commercial_area' or 'find_competitors'.

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/re171113-byte/startup-helper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server