bms-session-plugin 1.0.1 → 1.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/.mcp.json CHANGED
@@ -2,10 +2,7 @@
2
2
  "mcpServers": {
3
3
  "bms-session": {
4
4
  "command": "npx",
5
- "args": ["-y", "bms-session-mcp-server"],
6
- "env": {
7
- "BMS_SESSION_ID": "${BMS_SESSION_ID}"
8
- }
5
+ "args": ["-y", "bms-session-mcp-server"]
9
6
  }
10
7
  }
11
8
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bms-session-plugin",
3
- "version": "1.0.1",
3
+ "version": "1.0.3",
4
4
  "description": "Claude Code plugin for BMS Session API and HOSxP hospital databases",
5
5
  "files": [
6
6
  ".claude-plugin/",
@@ -5,20 +5,28 @@ description: This skill should be used when the user asks to "query HOSxP databa
5
5
 
6
6
  # BMS Session API — HOSxP Hospital Database Integration
7
7
 
8
- ## Purpose
9
-
10
- Provide guidance for querying and building applications against HOSxP hospital databases using the BMS Session API. HOSxP is the most widely used hospital information system in Thailand.
8
+ ## CRITICAL: Immediate Action Required
11
9
 
12
- ## When MCP Server Is Available
10
+ **Check if the MCP server `bms-session` is connected.** The server name in Claude Code is `plugin:bms-session-plugin:bms-session`.
13
11
 
14
- If the `bms-session` MCP server is connected, use its tools directly:
12
+ **If connected — DO NOT ask the user for a session ID.** The session is already authenticated. Start using tools immediately:
15
13
 
16
- 1. Read `bms://session-info` resource first to understand the database type and constraints
14
+ 1. Read the `bms://session-info` resource from server `plugin:bms-session-plugin:bms-session` to get database type and constraints
17
15
  2. Use `list_tables` with a pattern filter to discover relevant tables (e.g., `list_tables({ pattern: "patient*" })`)
18
16
  3. Use `describe_table` to understand column structure before writing queries
19
17
  4. Use `query` to execute SQL and return results
20
18
 
21
- Always use `LIMIT` to avoid returning excessive rows.
19
+ **If NOT connected** — then ask the user for a `bms-session-id` and help them set up the MCP server or use the REST API directly.
20
+
21
+ ## Purpose
22
+
23
+ Provide guidance for querying and building applications against HOSxP hospital databases using the BMS Session API. HOSxP is the most widely used hospital information system in Thailand.
24
+
25
+ ## Using MCP Tools
26
+
27
+ Always use `LIMIT` to avoid returning excessive rows. Always use the `pattern` parameter with `list_tables` — the database has thousands of tables.
28
+
29
+ When the user asks to "analyze the database", "show patient data", "query hospital data", or similar — start working immediately by calling the MCP tools. Do not ask unnecessary questions. Use list_tables and describe_table to discover the schema, then write and execute queries.
22
30
 
23
31
  ## When MCP Server Is Not Available
24
32