Skip to main content
Glama
seanshin0214

Dr. QuantMaster MCP Server

by seanshin0214

check_assumptions

Validate statistical assumptions like normality, homoscedasticity, and independence for your analysis method to ensure reliable results.

Instructions

통계 가정 점검 가이드 (정규성, 등분산, 독립성 등)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYes분석 방법
data_descriptionNo데이터 설명

Implementation Reference

  • Registration of the 'check_assumptions' tool in the tools array, including name, description, and input schema.
      name: "check_assumptions",
      description: "통계 가정 점검 가이드 (정규성, 등분산, 독립성 등)",
      inputSchema: {
        type: "object",
        properties: {
          method: { type: "string", description: "분석 방법" },
          data_description: { type: "string", description: "데이터 설명" },
        },
        required: ["method"],
      },
    },
  • Handler function that provides a checklist of statistical assumptions for the specified method and suggests diagnostic tests.
    function handleCheckAssumptions(args: Record<string, unknown>) {
      const method = args.method as string;
      return {
        method,
        assumptions_checklist: {
          ols: ["Linearity", "Normality of residuals", "Homoscedasticity", "Independence", "No multicollinearity"],
          logit: ["Binary DV", "Independence", "No multicollinearity", "Linearity in logit"],
          panel_fe: ["Strict exogeneity", "Time-invariant heterogeneity", "Within-variation"]
        }[method] || ["Method-specific assumptions - use search_stats_knowledge"],
        diagnostic_tests: ["검정 목록은 diagnose_regression 도구 사용"]
      };
    }
  • Input schema for the check_assumptions tool defining the expected parameters.
    inputSchema: {
      type: "object",
      properties: {
        method: { type: "string", description: "분석 방법" },
        data_description: { type: "string", description: "데이터 설명" },
      },
      required: ["method"],
    },
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 it's a 'guide' for checking assumptions, which suggests it might provide explanations or recommendations rather than perform computations, but it does not clarify output format, whether it requires data input, or any operational constraints (e.g., rate limits, permissions). This lack of detail is a significant gap for a tool with no structured behavioral hints.

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, efficient phrase in Korean that conveys the core purpose without unnecessary words. It is front-loaded with the main idea, though it could be slightly more structured (e.g., by specifying the tool's output). There is no wasted text, making it concise and easy to parse.

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 implied by statistical assumption checking, lack of annotations, and no output schema, the description is incomplete. It does not explain what the tool returns (e.g., a guide text, code, or diagnostic results), how to interpret outputs, or any behavioral nuances. This leaves the agent with insufficient context to use the tool effectively beyond basic parameter input.

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?

Schema description coverage is 100%, with parameters 'method' (analysis method) and 'data_description' (data description) documented in the schema. The description does not add any meaning beyond this, such as examples or constraints for the parameters. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to given the schema's completeness.

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

Purpose3/5

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

The description '통계 가정 점검 가이드 (정규성, 등분산, 독립성 등)' translates to 'Statistical assumption checking guide (normality, homoscedasticity, independence, etc.)', which provides a general purpose (guide for checking statistical assumptions) but is vague about the specific action (e.g., whether it generates code, explains methods, or performs tests). It distinguishes from siblings by focusing on assumption checking rather than other statistical tasks, but lacks a clear verb+resource combination.

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 offers no explicit guidance on when to use this tool versus alternatives. While it implies usage in statistical analysis contexts, it does not specify scenarios, prerequisites, or comparisons to sibling tools like 'diagnose_regression' or 'interpret_diagnostics', which might overlap. This leaves the agent without clear direction for tool selection.

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