Skip to main content
Glama
Hirao-Y

Poker Task Management MCP

by Hirao-Y

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
poker_proposeBodyC

新しい3D立体を提案します(自動バックアップ付き)

poker_updateBodyC

既存立体のパラメータを更新します

poker_deleteBodyB

立体を削除します(依存関係チェック付き)

poker_proposeZoneC

材料ゾーンを提案します(物理検証付き)

poker_updateZoneC

既存ゾーンの材料や密度を更新します

poker_deleteZoneB

ゾーンを削除します(ATMOSPHERE以外)

poker_proposeTransformC

回転・移動変換を提案します

poker_updateTransformC

既存変換の操作を更新します

poker_deleteTransformC

変換を削除します

poker_proposeBuildupFactorC

ビルドアップ係数を提案します

poker_updateBuildupFactorC

既存ビルドアップ係数の設定を更新します

poker_deleteBuildupFactorC

ビルドアップ係数を削除します

poker_changeOrderBuildupFactorC

ビルドアップ係数の順序を変更します

poker_proposeSourceD

新しい線源を提案します

poker_updateSourceC

既存放射線源のパラメータを更新します

poker_deleteSourceB

放射線源を削除します

poker_proposeDetectorC

新しい検出器を提案します

poker_updateDetectorC

既存検出器のパラメータを更新します

poker_deleteDetectorC

検出器を削除します

poker_applyChangesA

保留中の全変更を実際のYAMLファイルに適用します(自動バックアップ実行)

poker_proposeUnitA

単位設定セクションを提案します(YAMLファイルに未存在の場合のみ)- 4キー完全性保証

poker_getUnitB

現在の単位設定を取得します(4つのキーすべてを返却)- 完全性保証

poker_updateUnitB

既存単位設定を更新します(部分更新可能だが4つのキーは常に維持)- 完全性保証

poker_validateUnitIntegrityC

単位系の4キー完全性と物理的整合性を包括検証します

poker_analyzeUnitConversionC

異なる単位系間の変換係数を分析・計算します

poker_executeCalculationC

作成したYAMLファイルを使用してpoker_cuiで放射線遮蔽計算を実行します

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 26 tools

Disambiguation5/5

Every tool has a clearly distinct purpose targeting specific resources (Body, BuildupFactor, Detector, Source, Transform, Zone, Unit) and actions (analyze, apply, change, delete, execute, get, propose, update, validate). There is no ambiguity or overlap between tools, as each handles a unique operation on a specific entity in the radiation shielding calculation domain.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with the prefix 'poker_' (e.g., poker_deleteBody, poker_proposeDetector, poker_updateUnit). The naming is uniform across all 26 tools, using snake_case and clear action-resource combinations, making it highly predictable and readable.

Tool Count2/5

With 26 tools, the count is too high for typical MCP server scope, which usually benefits from 3-15 tools. While the domain (radiation shielding calculation) is complex, the tool set feels heavy and could overwhelm agents, suggesting potential over-fragmentation of operations.

Completeness5/5

The tool set provides complete CRUD/lifecycle coverage for the domain, including propose (create), get, update, and delete operations for all key entities (Body, BuildupFactor, Detector, Source, Transform, Zone, Unit), plus analysis, validation, and execution tools. There are no obvious gaps, ensuring agents can handle full workflows without dead ends.

Maintenance

ActivityActive
ResponsivenessNo issues