Skip to main content
Glama
enesjakozh
yamaton

mcp-dice

by yamaton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mcp-dice: Un servidor MCP para tirar dados

insignia de herrería captura de pantalla

Un servidor de Protocolo de Contexto de Modelo (MCP) que permite a los Modelos de Lenguaje Grandes (LLM) lanzar dados. Acepta la notación de dados estándar (p. ej., 1d20 ) y devuelve tanto las tiradas individuales como su suma.

Características

  • Admite notación de dados estándar (por ejemplo, 1d20 , 3d6 , 2d8+1 )

  • Devuelve tanto los rollos individuales como la suma total

  • Fácil integración con Claude Desktop

  • Compatible con MCP Inspector para depuración

Related MCP server: Globalping

Instalación

Instalación mediante herrería

Para instalar Dice Roller para Claude Desktop automáticamente a través de Smithery :

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

Hacer que uv esté disponible: https://docs.astral.sh/uv/getting-started/installation/

Uso

Uso básico de la línea de comandos

# Using uvx
uvx mcp-dice

Formato de entrada

El servidor acepta un objeto JSON con un campo notation :

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

Ejemplos de respuestas:

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

Configuración del escritorio de Claude

Ubicación

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

  • Ventanas: %APPDATA%/Claude/claude_desktop_config.json

Ejemplos

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

Nota: reemplace zsh con su shell de inicio de sesión.

Desarrollo y depuración

Instalación de dependencias de desarrollo

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

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

Ejecución de pruebas

uv run pytest

Uso del inspector MCP

El Inspector MCP es una herramienta útil para depurar su servidor MCP. Instálelo y ejecútelo con npm:

npx @modelcontextprotocol/inspector uvx mcp-dice

Configuración de escritorio de Claude para desarrollo

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

Nota: Reemplace path/to/mcp-dice-repo con la ruta al repositorio en su sistema de archivos.

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

Nota: Reemplace zsh con su shell de inicio de sesión. Además, reemplace path/to/mcp-dice-repo con la ruta al repositorio en su sistema de archivos 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