jb_gateway_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JB_GATEWAY_AUDIT_LOG | No | Path to the audit log (JSON Lines, one entry per tool call, secrets redacted). Parent directory is created automatically. | ~/.jb_gateway_mcp/audit.jsonl |
| JB_GATEWAY_CALLER_ID | No | Identity used for every policy check and audit entry in this process. Must match a `callers:` key in `policy.yaml` to be granted anything. | local |
| JB_GATEWAY_POLICY_FILE | No | Path to the policy file. | policy.yaml |
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 |
|---|---|
| pingA | Smoke-test tool confirming the gateway process is reachable. |
| gmail.list_messagesC | List Gmail messages for an account, optionally filtered by query. |
| gmail.read_messageA | Read a single Gmail message's subject/from/snippet/body. |
| gmail.send_messageC | Send an email from an account. |
| calendar.list_eventsA | List upcoming events on a calendar. |
| calendar.create_eventC | Create a new calendar event. |
| drive.list_filesB | List Drive files matching a query. |
| drive.read_fileB | Read metadata and text content of a Drive file. |
| bank.list_accountsB | List linked bank accounts for an institution (masked IBAN). |
| bank.get_balanceB | Get current/available balances for a bank account. |
| bank.summarize_spendingA | Aggregate total in/out/net spending for a date range (no transaction detail). |
| bank.list_transactions_summaryA | List transactions for a date range: date, amount, currency only. |
| bank.list_transactions_detailedC | List transactions including counterparty name/description (IBANs still masked). |
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 13 tools
Every tool is explicitly scoped by a domain prefix and a specific action; Gmail, Calendar, Drive, and Bank operations do not overlap. The two transaction-listing tools are differentiated as summary versus detailed.
Tools consistently follow a <domain>.<verb>_<object> pattern (e.g. gmail.list_messages, drive.read_file, bank.get_balance). The standalone ping is a minor conventional exception but fits the gateway smoke-test role.
Thirteen tools is a reasonable size for a multi-service gateway covering Gmail, Calendar, Drive, and banking data. Each tool contributes a distinct operation without bloat.
The read side is well covered, but the write/update side is incomplete: calendar events can be created but not updated or deleted, and Drive has no upload/update capability. Gmail and bank functionality are adequate for their apparent read/limited-action scope.