karte-datahub-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for streamable-http transport | 8080 |
| BQ_PROJECT | No | BigQuery クエリ実行用 GCP プロジェクト | |
| DATA_PROJECT | No | KARTE データプロジェクト | karte-data |
| KARTE_API_KEY | Yes | KARTE API キー | |
| MCP_TRANSPORT | No | MCP transport protocol (stdio or streamable-http) | stdio |
| CREDENTIAL_FILE | No | サービスアカウントキーファイルパス |
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 |
|---|---|
| query_karte_eventsA | KARTEイベントデータを取得する。 日付制約は自動的に適用される（デフォルト: 2日前〜昨日）。 Args: select_columns: SELECT句（デフォルト: "*"） where_clause: 追加WHERE条件（例: "event_name = 'click'"） date_from: 開始日 YYYYMMDD形式（デフォルト: 2日前） date_to: 終了日 YYYYMMDD形式（デフォルト: 昨日） limit: 取得件数上限 1〜10000（デフォルト: 100）。Noneで制限なし order_by: ORDER BY句（例: "sync_date DESC"） |
| count_karte_eventsB | KARTEイベントの件数を取得する。 Args: where_clause: WHERE条件（例: "event_name = 'purchase'"） date_from: 開始日 YYYYMMDD形式（デフォルト: 2日前） date_to: 終了日 YYYYMMDD形式（デフォルト: 昨日） group_by: GROUP BY句（例: "event_name"） |
| describe_karte_events_schemaA | KARTEイベントテーブルのスキーマを取得する。 テーブルのカラム名、型、説明等のメタデータを返す。 |
| execute_karte_sqlA | カスタムSQLを実行する（ガードレール付き）。 krt_pockyevent_v1_* テーブルへのクエリには _TABLE_SUFFIX 制約が必須。 LIMIT未指定時は自動で LIMIT 1000 が付与される。 破壊的SQL（DROP, DELETE等）は拒否される。 Args: sql: 実行するSQL文 dry_run: Trueの場合、スキャン量のみ確認する no_limit: Trueの場合、自動LIMIT付与をスキップする |
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 4 tools
The tools are mostly distinct: count_karte_events counts events, describe_karte_events_schema provides metadata, execute_karte_sql runs custom SQL, and query_karte_events retrieves event data. However, query_karte_events and execute_karte_sql could be confused as both retrieve data, though execute_karte_sql is more flexible with custom SQL while query_karte_events has structured parameters. The descriptions help clarify their boundaries.
All tool names follow a consistent verb_noun pattern with snake_case: count_karte_events, describe_karte_events_schema, execute_karte_sql, and query_karte_events. The naming is predictable and readable throughout the set.
With 4 tools, the count is reasonable for a data query server focused on KARTE events. It covers core operations like counting, describing schema, querying, and custom SQL execution. It might benefit from additional tools for more advanced analytics or data manipulation, but the scope is well-defined and manageable.
The toolset covers basic read operations for KARTE event data, including counting, schema description, structured querying, and custom SQL. However, there are notable gaps: no tools for writing or updating data (e.g., inserting or modifying events), and limited to event data without broader data management capabilities. Agents can work around this for query tasks but may fail for data manipulation needs.