Skip to main content
Glama
SAS-AII

mcp-server

by SAS-AII
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TAVILY_API_KEYYesYour Tavily API key for web search capabilities.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
web_searchB

Search the web for information about the given query.

Parameters:

  • query: The search query

Example:

  • web_search("What is the capital of France?")

roll_diceA

Roll dice with the given notation.

Parameters:

  • notation: Dice notation like "2d6+1"

  • num_rolls: Number of times to roll (default 1)

Example:

  • roll_dice("3d6", 2)

chess_player_statsC

Get your Chess.com profile and ratings summary.

Example:

  • chess_player_stats()

chess_recent_matchesB

List your most recent games.

Parameters:

  • limit: Number of games to list (default 5)

Example:

  • chess_recent_matches(3)

chess_last_matchA

Show details about your most recent finished game.

Example:

  • chess_last_match()

chess_analyze_recent_gameC

Run engine analysis on one of your recent games (0 = latest).

Parameters:

  • game_index: Which recent game to analyze (0 = latest)

  • movetime_ms: Time per move for engine analysis in milliseconds (default 500)

Example:

  • chess_analyze_recent_game(0, 700)

chess_analyze_pgnC

Analyze a single PGN string with Stockfish.

Parameters:

  • pgn_string: The PGN of the game to analyze

  • movetime_ms: Time per move for engine analysis (default 500)

Example:

  • chess_analyze_pgn("[Event ...] 1. e4 e5 ...", 300)

chess_analyze_game_idA

Analyze a Chess.com game by its game ID using Stockfish.

Parameters:

  • game_id: The Chess.com game ID (UUID or numeric) from the game's URL

  • movetime_ms: Time per move for engine analysis (default 500)

Example:

  • chess_analyze_game_id("141227700772", 300)

chess_analyze_multiple_pgnA

Analyze multiple PGNs separated by '---', '###', or triple newlines.

Parameters:

  • pgn_strings: One or more PGNs separated by a supported delimiter

  • movetime_ms: Time per move for engine analysis (default 500)

Example:

  • chess_analyze_multiple_pgn("PGN1 --- PGN2", 300)

chessA

Unified Chess tool (prefer the specific chess_* tools instead).

Supported actions and params:

  • recent_matches: {"limit": int = 5}

  • last_match: {}

  • player_stats: {}

  • analyze_recent_game: {"game_index": int = 0, "movetime_ms": int = 500}

  • analyze_pgn: {"pgn_string": str, "movetime_ms": int = 500}

  • analyze_multiple_pgn: {"pgn_strings": str, "movetime_ms": int = 500}

Examples:

  • chess("recent_matches", {"limit": 3})

  • chess("player_stats")

  • chess("analyze_recent_game", {"game_index": 0, "movetime_ms": 700})

  • chess("analyze_pgn", {"pgn_string": "[Event ...] 1. e4 e5 ...", "movetime_ms": 500})

  • chess("analyze_multiple_pgn", {"pgn_strings": "PGN1 --- PGN2"})

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

B3.1/5.0

Scored across 10 tools

Disambiguation3/5

Most chess tools are clearly distinct (stats, matches, analysis by PGN or ID), but the generic 'chess' tool duplicates all their functionality, creating ambiguity about which tool to use. web_search and roll_dice are unrelated and easy to distinguish.

Naming Consistency3/5

web_search and roll_dice use verb_noun pattern consistently. Chess tools mostly follow chess_verb_noun but include exceptions like 'chess_player_stats' (noun_noun) and 'chess_recent_matches' (adjective_noun). The plain 'chess' tool breaks the pattern entirely.

Tool Count3/5

10 tools is a reasonable number, but the inclusion of the redundant 'chess' tool and the mix of unrelated domains (web search, dice, chess) makes the surface feel slightly bloated. Could be streamlined by removing the generic chess tool.

Completeness3/5

The chess subdomain covers stats, recent matches, and PGN analysis well, but lacks features like game archiving or move-by-move play. web_search and roll_dice are single-purpose and complete. Overall the surface is adequate but not deep in any area.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources