tcs_mcp_claude
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TCS_MODE | No | 実行モード: local または ssh | local |
| TCS_SSH_HOST | No | SSH ホスト名（ssh モード時） | genkai.cc.kyushu-u.ac.jp |
| TCS_SSH_USER | No | SSH ユーザ名（ssh モード時、必須） | |
| TCS_WORK_DIR | No | ジョブ出力ファイルを探す作業ディレクトリ | ~/work |
| TCS_LOG_LEVEL | No | ログレベル | INFO |
| TCS_PJDEL_PATH | No | pjdel の絶対パス | /usr/local/bin/pjdel |
| TCS_PJSUB_PATH | No | pjsub の絶対パス | /usr/local/bin/pjsub |
| TCS_PJSTAT_PATH | No | pjstat の絶対パス | /usr/local/bin/pjstat |
| TCS_SSH_KEY_FILE | No | SSH 秘密鍵パス | ~/.ssh/id_rsa |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_jobA | Submit a batch job to the TCS/PJM scheduler on Genkai. Provide the full job script content. Resource directives in the script take precedence over the parameters here. The parameters are ignored when the script already contains #PJM directives. Returns: {"job_id": str, "message": str} |
| list_jobsA | List jobs for the current user. history_days: include completed jobs from the past N days (max 90). rscgrp: filter by resource group name. Returns list of job dicts with keys: job_id, job_name, md, st, user, start_date, elapse_lim, node_require, vnode, core, v_mem. |
| get_job_statusA | Get status of a specific job by ID. Returns list of job dicts (same format as list_jobs). Raises RuntimeError if the job is not found. |
| delete_jobC | Delete (cancel) a queued or running job. Returns: {"success": bool, "job_id": str, "message": str} |
| get_resource_groupsA | List available resource groups and their sizes on Genkai. rscgrp: filter by specific resource group name. Returns list of dicts with keys: rscunit, rscunit_size, rscgrp, rscgrp_size. |
| get_quota_limitsC | Get quota and limit information for the current user. Returns a dict with sections: USER, GROUP, ALL. Each section contains a list of {limit_name, limit, alloc} dicts. |
| list_filesA | List files in a work directory. directory: path to list (defaults to work_dir). pattern: glob pattern to filter filenames. Returns list of {path, name, is_dir} dicts. |
| read_fileA | Read a text file from the Genkai filesystem. Only files within work_dir are accessible. Returns {content, truncated, size_bytes}. |
| read_job_outputA | Read the stdout or stderr output file of a completed job. Searches for output files by common PJM naming patterns: .out / .err STDIN.out / .err Returns {content, truncated, path}. |
| generate_job_templateA | Generate a PJM job script template for Genkai. Available rscgrps: a-batch-low, a-batch, b-batch-low, b-batch, b-batch-mig-low, b-batch-mig, c-batch-low, c-batch, and their -inter variants. Returns a shell script string with #PJM directives ready to submit with pjsub. |
| list_resource_groupsB | List all known Genkai resource groups and their type (cpu/gpu/gpu_mig). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes: file operations, job lifecycle, and resource queries are clearly separated. However, list_resource_groups and get_resource_groups both list resource groups but with differing details, which could cause misselection.
Tool names generally follow a consistent verb_noun pattern in snake_case, such as list_files, submit_job, delete_job. The overlap between list_resource_groups and get_resource_groups introduces slight inconsistency, but the overall pattern is predictable.
Eleven tools is well within the ideal range for a domain-specific server covering file access and job management. Each tool serves a clear purpose without unnecessary bloat.
The surface covers the full job lifecycle: template generation, submission, listing, status check, output retrieval, and deletion. Additionally, resource group and quota queries address administrative needs. No obvious dead ends.