Skip to main content
Glama
seanshin0214

Dr. QuantMaster MCP Server

by seanshin0214

suggest_method

Recommends statistical methods based on research questions and data characteristics for quantitative analysis.

Instructions

연구질문과 데이터 특성에 맞는 통계 방법 추천

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
research_questionYes연구 질문
dv_typeYes종속변수 유형
data_structureNo데이터 구조
causal_designNo인과추론 설계

Implementation Reference

  • Registration of the 'suggest_method' tool in the tools array, including its name, description, and input schema.
    {
      name: "suggest_method",
      description: "연구질문과 데이터 특성에 맞는 통계 방법 추천",
      inputSchema: {
        type: "object",
        properties: {
          research_question: { type: "string", description: "연구 질문" },
          dv_type: {
            type: "string",
            enum: ["continuous", "binary", "ordinal", "count", "time_to_event", "proportion"],
            description: "종속변수 유형"
          },
          data_structure: {
            type: "string",
            enum: ["cross_sectional", "panel", "time_series", "clustered", "multilevel"],
            description: "데이터 구조"
          },
          causal_design: {
            type: "string",
            enum: ["none", "experimental", "quasi_experimental", "observational"],
            description: "인과추론 설계"
          },
        },
        required: ["research_question", "dv_type"],
      },
    },
  • Input schema definition for the 'suggest_method' tool specifying parameters for research question, dependent variable type, data structure, and causal design.
    inputSchema: {
      type: "object",
      properties: {
        research_question: { type: "string", description: "연구 질문" },
        dv_type: {
          type: "string",
          enum: ["continuous", "binary", "ordinal", "count", "time_to_event", "proportion"],
          description: "종속변수 유형"
        },
        data_structure: {
          type: "string",
          enum: ["cross_sectional", "panel", "time_series", "clustered", "multilevel"],
          description: "데이터 구조"
        },
        causal_design: {
          type: "string",
          enum: ["none", "experimental", "quasi_experimental", "observational"],
          description: "인과추론 설계"
        },
      },
      required: ["research_question", "dv_type"],
    },
  • The core handler function for 'suggest_method' that provides statistical method recommendations based on input parameters using a predefined suggestions lookup table.
    function handleSuggestMethod(args: Record<string, unknown>) {
      const dvType = args.dv_type as string;
      const dataStructure = (args.data_structure as string) || "cross_sectional";
      const causalDesign = (args.causal_design as string) || "none";
    
      const suggestions: Record<string, any> = {
        continuous: {
          cross_sectional: {
            observational: ["OLS Regression", "Robust Regression"],
            quasi_experimental: ["Propensity Score Matching", "IV/2SLS"],
            experimental: ["t-test", "ANOVA", "OLS with controls"]
          },
          panel: {
            observational: ["Panel FE/RE", "Correlated Random Effects"],
            quasi_experimental: ["DID", "Synthetic Control", "Event Study"]
          },
          time_series: {
            observational: ["ARIMA", "VAR", "VECM"],
            quasi_experimental: ["Interrupted Time Series", "Event Study"]
          }
        },
        binary: {
          cross_sectional: {
            observational: ["Logistic Regression", "Probit"],
            quasi_experimental: ["PSM + Logit", "IV Probit"]
          },
          panel: {
            observational: ["Conditional Logit (FE)", "Random Effects Logit"],
            quasi_experimental: ["DID Logit", "Linear Probability Model + FE"]
          }
        },
        count: {
          cross_sectional: {
            observational: ["Poisson", "Negative Binomial", "Zero-Inflated"]
          },
          panel: {
            observational: ["FE Poisson", "FE Negative Binomial"]
          }
        }
      };
    
      const methodList = suggestions[dvType]?.[dataStructure]?.[causalDesign] ||
        suggestions[dvType]?.[dataStructure]?.["observational"] ||
        ["검색 필요: search_stats_knowledge 사용"];
    
      return {
        research_question: args.research_question,
        dv_type: dvType,
        data_structure: dataStructure,
        causal_design: causalDesign,
        recommended_methods: methodList,
        considerations: [
          "데이터 크기와 분포 확인 필요",
          "가정 검토 (내생성, 선택편의 등)",
          "robustness check 계획 수립"
        ]
      };
    }
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 of behavioral disclosure. It states the tool '추천' (recommends) methods, which implies a read-only, advisory function, but does not detail output format, limitations, or potential side effects. For a tool with 4 parameters and no output schema, this lack of behavioral context is a significant gap, as the agent cannot anticipate what the recommendation will entail.

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: '연구질문과 데이터 특성에 맞는 통계 방법 추천'. It is front-loaded and wastes no words, efficiently conveying the core purpose without redundancy. Every part of the sentence contributes directly to understanding the tool's function.

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 of statistical method recommendation, the description is incomplete. It lacks details on output (no output schema provided), behavioral traits, and usage context. With no annotations and many sibling tools, the description does not provide enough information for an AI agent to fully understand how to invoke or interpret results, making it inadequate for the tool's intended function.

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 input schema has 100% description coverage, with clear enum values and descriptions for parameters like 'dv_type' and 'data_structure'. The description adds no additional semantic information beyond the schema, such as examples or usage tips. With high schema coverage, the baseline score is 3, as the schema adequately documents parameters without extra help from the description.

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: '연구질문과 데이터 특성에 맞는 통계 방법 추천' (Recommend statistical methods suitable for research questions and data characteristics). It specifies the verb '추천' (recommend) and the resource '통계 방법' (statistical methods), making the intent unambiguous. However, it does not explicitly differentiate from sibling tools like 'compare_methods' or 'test_selection', which might offer similar functionality, so it falls short of a perfect score.

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. With many sibling tools related to statistical methods (e.g., 'compare_methods', 'test_selection', 'get_method_guide'), there is no indication of context, prerequisites, or exclusions. Usage is implied by the tool's name and description but not explicitly stated, leaving gaps for an AI agent to infer correctly.

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/seanshin0214/quantmaster-mcp-server'

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