Skip to main content
Glama
seanshin0214

Dr. QuantMaster MCP Server

by seanshin0214

mlm_guide

Guide to multilevel modeling with ICC calculation, random effects specification, and cross-level interaction analysis for hierarchical data structures.

Instructions

다층모형 가이드 (ICC, 랜덤효과, 교차수준 상호작용)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelsYes수준 수 (2 or 3)
random_effectsNo랜덤효과
cross_levelNo교차수준 상호작용

Implementation Reference

  • Registration of the 'mlm_guide' tool in the exported tools array, including name, description, and input schema.
    {
      name: "mlm_guide",
      description: "다층모형 가이드 (ICC, 랜덤효과, 교차수준 상호작용)",
      inputSchema: {
        type: "object",
        properties: {
          levels: { type: "number", description: "수준 수 (2 or 3)" },
          random_effects: { type: "array", items: { type: "string" }, description: "랜덤효과" },
          cross_level: { type: "boolean", description: "교차수준 상호작용" },
        },
        required: ["levels"],
      },
    },
  • Input schema for the mlm_guide tool defining parameters: levels (required), random_effects, cross_level.
    inputSchema: {
      type: "object",
      properties: {
        levels: { type: "number", description: "수준 수 (2 or 3)" },
        random_effects: { type: "array", items: { type: "string" }, description: "랜덤효과" },
        cross_level: { type: "boolean", description: "교차수준 상호작용" },
      },
      required: ["levels"],
    },
  • Handler function that executes the mlm_guide tool, providing key multilevel modeling concepts (ICC, random slopes, cross-level interactions) and example lme4 R code.
    function handleMlmGuide(args: Record<string, unknown>) {
      return {
        levels: args.levels,
        key_concepts: {
          icc: "Intraclass Correlation - 집단간 분산 비율",
          random_slope: "기울기의 집단간 변이 허용",
          cross_level: "수준간 상호작용"
        },
        r_code: "library(lme4)\nfit <- lmer(y ~ x1 + (1 + x1 | group), data = df)"
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions concepts (ICC, random effects, cross-level interactions) but doesn't disclose behavioral traits like output format (e.g., text, code, visualization), interactivity, or prerequisites (e.g., data input). This leaves the agent guessing about how the tool behaves when invoked.

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 with a single phrase listing key concepts, which is efficient and front-loaded. However, it could be more structured by clarifying the tool's action (e.g., 'Generate guidance for...') to improve readability.

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 no annotations, no output schema, and a tool with 3 parameters (one required), the description is incomplete. It doesn't explain what the tool returns (e.g., explanations, code snippets, recommendations) or how parameters affect the output, leaving significant gaps for the agent to understand the tool's functionality.

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%, so the schema already documents all parameters (levels, random_effects, cross_level). The description doesn't add meaning beyond what the schema provides, such as explaining how parameters influence the guidance or providing examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 states the tool provides guidance for multilevel modeling concepts (ICC, random effects, cross-level interactions), which gives a general purpose. However, it's vague about what specific guidance it offers (e.g., interpretation, implementation, selection) and doesn't distinguish from siblings like 'sem_guide' or 'bayesian_guide' that also provide statistical guidance.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies it's for multilevel modeling contexts, but it doesn't specify scenarios (e.g., planning, analysis, reporting) or compare to siblings like 'get_method_guide' or 'suggest_method'. Usage is only loosely inferred from the topic.

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