Skip to main content
Glama
enesjakozh
yamaton

mcp-dice

by yamaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mcp-dice: サイコロを振るためのMCPサーバー

鍛冶屋のバッジ スクリーンショット

大規模言語モデル（LLM）がサイコロを振れるようにするモデルコンテキストプロトコル（MCP）サーバー。標準的なサイコロ表記（例： 1d20 ）を受け付け、個々の出目とその合計を返します。

特徴

  • 標準的なサイコロ表記法3d6サポート（例： 1d20``2d8+1 ）

  • 個々のロールと合計の両方を返します

  • Claude Desktopとの簡単な統合

  • デバッグ用のMCP Inspectorと互換性あり

Related MCP server: Globalping

インストール

Smithery経由でインストール

Smithery経由で Claude Desktop 用の Dice Roller を自動的にインストールするには:

npx @smithery/cli install mcp-dice --client claude

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

  • Windows: %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インスペクターの使用

MCP Inspectorは、MCPサーバーのデバッグに役立つツールです。npmを使ってインストールして実行してください。

npx @modelcontextprotocol/inspector uvx mcp-dice

開発のためのClaudeデスクトップ構成

{
  "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