Skip to main content
Glama
seanshin0214

Dr. QuantMaster MCP Server

by seanshin0214

replication_package

Generate structured replication packages for quantitative research by specifying required components like code, data, and documentation to ensure reproducibility.

Instructions

재현성 패키지 구조 가이드

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
journalNo목표 저널
componentsYes포함 요소 (code, data, readme, codebook)

Implementation Reference

  • The handler function implementing the 'replication_package' tool logic. It returns a predefined replication package folder structure based on the input components.
    function handleReplicationPackage(args: Record<string, unknown>) {
      return {
        components: args.components,
        structure: {
          code: "/code - Analysis scripts",
          data: "/data - Raw and processed data",
          output: "/output - Tables and figures",
          docs: "/docs - README, codebook"
        }
      };
    }
  • Registration of the 'replication_package' tool in the tools array, including its name, description, and input schema definition.
    {
      name: "replication_package",
      description: "재현성 패키지 구조 가이드",
      inputSchema: {
        type: "object",
        properties: {
          journal: { type: "string", description: "목표 저널" },
          components: {
            type: "array",
            items: { type: "string" },
            description: "포함 요소 (code, data, readme, codebook)"
          },
        },
        required: ["components"],
      },
    },
  • Input schema definition for the 'replication_package' tool, specifying properties like journal and components, with components required.
    inputSchema: {
      type: "object",
      properties: {
        journal: { type: "string", description: "목표 저널" },
        components: {
          type: "array",
          items: { type: "string" },
          description: "포함 요소 (code, data, readme, codebook)"
        },
      },
      required: ["components"],
    },
  • Dispatch case in the main handleToolCall function that routes calls to the replication_package handler.
    case "replication_package":
      return handleReplicationPackage(args);
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. The description only hints at providing guidance on structure but doesn't specify if this tool generates files, outputs text, requires specific inputs beyond the schema, or has any side effects (e.g., file creation). For a tool with no annotation coverage, this lack of detail on behavior is a significant gap, leaving the agent uncertain about what the tool actually does beyond its inputs.

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 is front-loaded and wastes no words. However, it's overly concise to the point of under-specification, lacking necessary detail for clarity. While structurally sound, it could benefit from additional context to improve usefulness without becoming verbose.

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 the tool name and sibling tools, the description is incomplete. With no annotations and no output schema, the description doesn't explain what the tool returns (e.g., a guide document, structured output, or file paths) or its behavioral traits. For a tool that likely involves guidance generation, this leaves critical gaps in understanding how to use it effectively in context.

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 documentation for 'journal' (target journal) and 'components' (included elements like code, data). The description doesn't add any meaning beyond this—it doesn't explain parameter interactions, provide examples, or clarify semantics. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description neither compensates nor detracts from the schema's information.

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 '재현성 패키지 구조 가이드' (Replication package structure guide) is vague—it suggests guidance on structure but lacks a specific verb and resource. It doesn't clearly state what the tool does (e.g., generates, validates, or explains a replication package), and it fails to distinguish from siblings like 'create_project_structure' or 'code_template', which might overlap in purpose. This is closer to a tautology of the tool name than a clear functional statement.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention context, prerequisites, or exclusions, and it doesn't reference sibling tools (e.g., 'create_project_structure' for general project setup or 'journal_guide' for journal-specific requirements). Without this, an agent must infer usage from the tool name alone, which is insufficient for effective 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