Skip to main content
Glama
enesjakozh
yamaton

mcp-dice

by yamaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mcp-dice: 주사위 굴리기용 MCP 서버

대장간 배지 스크린샷

대규모 언어 모델(LLM)이 주사위를 굴릴 수 있도록 하는 모델 컨텍스트 프로토콜(MCP) 서버입니다. 표준 주사위 표기법(예: 1d20 )을 사용하며, 개별 주사위 굴림 결과와 그 합을 반환합니다.

특징

  • 표준 주사위 표기법(예: 1d20 , 3d6 , 2d8+1 )을 지원합니다.

  • 개별 롤과 총합을 모두 반환합니다.

  • Claude Desktop과의 간편한 통합

  • 디버깅을 위한 MCP Inspector와 호환

Related MCP server: Globalping

설치

Smithery를 통해 설치

Smithery 를 통해 Claude Desktop용 Dice Roller를 자동으로 설치하려면:

지엑스피1

uv 사용 가능하게 설정하세요: https://docs.astral.sh/uv/getting-started/installation/

용법

기본 명령줄 사용법

# Using uvx
uvx mcp-dice

입력 형식

서버는 notation 필드가 있는 JSON 객체를 허용합니다.

{
  "notation": "2d6+3"
}

응답 예시:

{
  "rolls": [
    3,
    1
  ],
  "sum": 4,
  "modifier": 3,
  "total": 7,
  "notation": "2d6+3",
  "timestamp": "2024-12-03T16:36:38.926452"
}

클로드 데스크톱 구성

위치

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • 윈도우: %APPDATA%/Claude/claude_desktop_config.json

예시

{
  "mcpServers": {
    "dice": {
      "command": "uvx",
      "args": ["mcp-dice"]
    }
  }
}
{
  "mcpServers": {
    "dice": {
      "command": "wsl",
      "args": [
        "-e",
        "zsh",
        "-lc",
        "uvx mcp-dice"
      ]
    }
  }
}

참고: zsh 로그인 셸로 바꾸세요.

개발 및 디버깅

개발 종속성 설치

# Clone the repository
git clone https://github.com/yourusername/mcp-dice
cd mcp-dice

# Install development dependencies
uv pip install -e ".[dev]"

테스트 실행

uv run pytest

MCP Inspector 사용

MCP Inspector는 MCP 서버 디버깅에 유용한 도구입니다. npm을 사용하여 설치하고 실행하세요.

npx @modelcontextprotocol/inspector uvx mcp-dice

개발을 위한 Claude Desktop 구성

{
  "mcpServers": {
    "dice": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "path/to/mcp-dice-repo",
        "mcp-dice"
      ]
    }
  }
}

참고: path/to/mcp-dice-repo 파일 시스템의 저장소 경로로 바꾸세요.

{
  "mcpServers": {
    "dice": {
      "command": "wsl",
      "args": [
        "-e",
        "zsh",
        "-lc",
        "uv run --directory path/to/mcp-dice-repo mcp-dice"
      ]
    }
  }
}

참고: zsh 로그인 셸로 바꾸세요. 또한, path/to/mcp-dice-repo WSL 파일 시스템의 저장소 경로로 바꾸세요.

Available Tools

1 tool
roll_diceA

Roll dice using standard notation (e.g., '2d6+3', '1d20-2')

ParametersJSON Schema
NameRequiredDescriptionDefault
notationYesDice notation (e.g., '2d6+3', '1d20-2')

TDQS

A3.5/5.0
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. It describes the action but lacks behavioral details such as whether this is a deterministic or random process, any rate limits, or what the output format might be. The description is minimal and does not compensate for the absence of annotations.

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, efficient sentence that front-loads the purpose and provides clear examples. There is no wasted information, making it appropriately concise and well-structured for its purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is adequate but has gaps. It explains the input but lacks details on output or behavioral context, making it minimally viable but not fully complete for an agent to understand all aspects without additional inference.

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 schema description coverage is 100%, so the schema already documents the single parameter 'notation' with a description and pattern. The description adds minimal value by restating the parameter concept with examples, aligning with the baseline score when schema coverage is high.

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

Purpose5/5

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

The description clearly states the specific action ('Roll dice') and resource ('using standard notation'), with examples provided. It precisely defines what the tool does without being tautological, and since there are no sibling tools, no differentiation is needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by providing examples of dice notation, but it does not explicitly state when to use this tool versus alternatives. Since there are no sibling tools, no explicit alternatives are mentioned, leaving usage context somewhat implied rather than fully guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedroll_dice
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'roll_dice' has a clearly distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The naming follows a consistent verb_noun pattern with 'roll_dice', and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable for this single-tool server.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and can feel thin. For a dice-rolling server, while the core operation is covered, additional tools like rolling multiple dice types or retrieving roll history could enhance completeness, making the count borderline inappropriate.

Completeness3/5

The tool covers the basic dice-rolling functionality well, but there are notable gaps. For example, there are no tools for listing available dice types, saving roll results, or performing statistical analysis on rolls, which could be expected in a more comprehensive dice-rolling domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches