saga-event-space-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAGA_EVENT_SPACE_BASE_URL | No | API base URL (default: https://saga-event-space.midnight480.com) | https://saga-event-space.midnight480.com |
| SAGA_EVENT_SPACE_API_TOKEN | Yes | API access token required for all operations including search |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_placesA | 佐賀県内のイベントスペース・ホテル・懇親会会場を検索します。キーワード、カテゴリ、設備条件、料金、収容人数などで絞り込みが可能です。 |
| get_place_detailB | 指定したIDの会場の詳細情報を取得します。 |
| list_announcementsA | お知らせの一覧を取得します。レベルやアクティブ状態で絞り込みが可能です。 |
| list_release_notesA | リリースノートの一覧を取得します。 |
| get_release_noteA | 指定したIDのリリースノートの詳細を取得します。 |
| check_healthB | Saga Event Space APIのシステム稼働状況を確認します。 |
| create_placeC | 新しい会場を作成します。APIトークンが必要です。 |
| update_placeC | 既存の会場情報を更新します。APIトークンが必要です。 |
| delete_placeA | 会場を削除します。APIトークンが必要です。この操作は取り消せません。 |
| get_place_statsA | 会場のステータスごとの件数統計を取得します。APIトークンが必要です。 |
| bulk_update_statusA | 複数の会場のステータスを一括で更新します。APIトークンが必要です。 |
| create_announcementB | 新しいお知らせを作成します。APIトークンが必要です。 |
| update_announcementB | 既存のお知らせを更新します。APIトークンが必要です。 |
| delete_announcementA | お知らせを削除します。APIトークンが必要です。この操作は取り消せません。 |
| create_release_noteB | 新しいリリースノートを作成します。APIトークンが必要です。 |
| update_release_noteB | 既存のリリースノートを更新します。APIトークンが必要です。 |
| delete_release_noteA | リリースノートを削除します。APIトークンが必要です。この操作は取り消せません。 |
| get_audit_logsB | Get a list of audit logs. Can be filtered by entity_type, user_id, action, etc. API token required. |
| get_audit_log_statsB | Get statistics of audit logs. API token required. |
| get_deletion_requestsA | Get a list of place deletion requests. API token required. |
| approve_deletion_requestA | Approve a pending deletion request. API token required. |
| reject_deletion_requestA | Reject a pending deletion request. API token required. |
| get_duplicatesA | Get a list of duplicate place reports. API token required. |
| report_duplicateB | Report a place as a duplicate. API token required. |
| resolve_duplicateC | Resolve a duplicate report. API token required. |
| merge_duplicateC | Merge a duplicate place. API token required. |
| get_usersC | Get a list of users. API token required. |
| update_user_roleB | Update the role of a user. API token required. |
| restore_userA | Restore a deleted user. API token required. |
| get_tokensA | Get a list of API tokens for the authenticated user. API token required. |
| create_tokenA | Create a new API token. API token required. The token secret is shown only once. |
| update_tokenA | Update the name of an existing API token. API token required. |
| delete_tokenB | Delete an API token. API token required. |
| normalize_addressC | Normalize a Japanese address string into structured components. |
| geocodeA | Convert an address into geographic coordinates (latitude and longitude). |
| get_upload_urlA | Get a presigned URL to upload a photo directly to R2. API token required. |
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 36 tools
Most tools clearly combine a resource with an action, so places, announcements, release notes, tokens, users, audit logs, deletion requests, and duplicates are generally easy to tell apart. A few workflow-adjacent pairs (approve_deletion_request vs delete_place, resolve_duplicate vs merge_duplicate, update_place vs bulk_update_status) share boundary behavior and could cause an agent to pick the wrong one without careful reading.
Tool names almost universally follow a snake_case verb_noun pattern (create_place, update_announcement, delete_token), and list/get usage is mostly consistent. Minor deviations exist: collection listing uses list_ for announcements/release_notes but get_ for tokens/users/audit_logs, and geocode is a lone bare verb.
36 tools is well beyond the comfortable MCP scope and mixes content CRUD, auth/token administration, user management, audit logs, moderation workflows, and address utilities into one server. While no tool is redundant, the surface is too large for an agent to quickly select among eight subdomains.
Core lifecycles are well covered for places (search/detail/create/update/delete/stats), announcements, release notes, tokens, and moderation queues. The notable gap is no get_announcement_detail endpoint, and user management is limited to list/update_role/restore without user creation or deletion, but these can be worked around.