Skip to main content
Glama
seanshin0214

Dr. QuantMaster MCP Server

by seanshin0214

bayesian_guide

Guide Bayesian analysis by selecting priors, running convergence diagnostics, and interpreting results for statistical modeling.

Instructions

베이지안 분석 가이드 (사전분포, 수렴진단, 해석)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
analysis_typeYes분석 유형
prior_typeNo사전분포
convergenceNo수렴진단 포함

Implementation Reference

  • The handler function that executes the bayesian_guide tool. It returns guidance on priors, convergence checks, and sample R code using brms.
    function handleBayesianGuide(args: Record<string, unknown>) {
      return {
        analysis_type: args.analysis_type,
        prior_type: args.prior_type,
        convergence_checks: ["Rhat < 1.01", "ESS > 400", "Trace plots", "Posterior predictive checks"],
        r_code: "library(brms)\nfit <- brm(y ~ x1 + x2, data = df, family = gaussian())"
      };
    }
  • The tool registration in the exported tools array, including name, description, and input schema.
      name: "bayesian_guide",
      description: "베이지안 분석 가이드 (사전분포, 수렴진단, 해석)",
      inputSchema: {
        type: "object",
        properties: {
          analysis_type: { type: "string", description: "분석 유형" },
          prior_type: { type: "string", enum: ["uninformative", "weakly_informative", "informative"], description: "사전분포" },
          convergence: { type: "boolean", description: "수렴진단 포함" },
        },
        required: ["analysis_type"],
      },
    },
  • The input schema defining parameters for the bayesian_guide tool: analysis_type (required), prior_type, convergence.
    inputSchema: {
      type: "object",
      properties: {
        analysis_type: { type: "string", description: "분석 유형" },
        prior_type: { type: "string", enum: ["uninformative", "weakly_informative", "informative"], description: "사전분포" },
        convergence: { type: "boolean", description: "수렴진단 포함" },
      },
      required: ["analysis_type"],
    },
  • The switch case in handleToolCall that routes calls to the bayesian_guide handler.
      return handleBayesianGuide(args);
    case "ml_for_causal":
Behavior1/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. However, the description only lists parameter names ('사전분포, 수렴진단, 해석') without explaining what the tool does behaviorally—e.g., whether it generates code, provides explanations, runs analyses, or requires specific data inputs. This leaves the agent with no understanding of the tool's actions or traits.

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 that lists key aspects without unnecessary words. It's appropriately sized for a tool with 3 parameters and no output schema, though it could be more front-loaded with purpose rather than parameter names. There's minimal waste, but it lacks structural clarity in conveying intent.

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 Bayesian analysis and the lack of annotations or output schema, the description is incomplete. It fails to explain what the tool produces (e.g., a guide document, code snippets, diagnostic plots) or how it integrates with other tools. For a statistical guidance tool with no behavioral context, this leaves significant gaps for an agent to understand its role and outputs.

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 with descriptions. The description lists parameter names ('사전분포, 수렴진단, 해석') but adds no meaningful semantics beyond what's in the schema—it doesn't clarify usage, constraints, or interactions. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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

Purpose2/5

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

The description '베이지안 분석 가이드 (사전분포, 수렴진단, 해석)' translates to 'Bayesian analysis guide (prior distribution, convergence diagnosis, interpretation)', which is a tautology that restates the tool name 'bayesian_guide' and lists input parameters rather than specifying what the tool actually does. It doesn't distinguish this Bayesian guide from sibling tools like 'ml_for_causal' or 'sem_guide' that might also involve 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 Guidelines1/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 doesn't mention any context, prerequisites, or exclusions, and with many sibling tools available (e.g., 'get_method_guide', 'suggest_method'), there's no indication of how this Bayesian-specific guide fits into broader workflows or when it's preferred over other methods.

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