SAP MCP Server

SAP Chat Status

sap_chat_status

Retrieve the SAP memory session status for any chat room to monitor active sessions and participant connections.

Instructions

Get backing SAP memory session status for a chat room.

Input Schema

TableJSON Schema

Name	Required	Description
`topic`	No	Thematic topic, for example openbook:sol-usdc:market-makers or sap:registry:discovery.
`roomId`	No	Optional explicit room ID. If omitted, one is derived deterministically.
`roomKind`	No	Chat room kind: dm, group, or room.
`roomName`	No	Human-readable room name for public thematic rooms.
`participants`	No	Participant agent/wallet identifiers for DM or group rooms.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes	MCP content blocks returned to the caller.
`isError`	No	True when the tool result represents an application-level error.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.4Jul 14, 2026

addedInput schema / properties / participants / items / description
```
Added value: +"Participants parameter for SAP Chat Status."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "description": "MCP content blocks returned to the caller.",
+      "items": {
+        "properties": {
+          "text": {
+            "description": "Human-readable JSON or text returned by the tool.",
+            "type": "string"
+          },
+          "type": {
+            "description": "MCP content block type, usually text.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "description": "True when the tool result represents an application-level error.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "content"
+  ],
+  "type": "object"
+}

Addedv0.5.0Jul 4, 2026

TDQS

C2.6/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description says 'Get' implying a read operation, but annotations set readOnlyHint=false, contradicting that. No additional behavioral details (e.g., side effects, idempotency) are disclosed beyond the annotation contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks structure. It front-loads the purpose but could be more informative without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema and 5 parameters, the description is too brief. It does not explain what the status represents or how to interpret the output, leaving the agent under-informed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers all 5 parameters with descriptions (100% coverage), so the description adds no extra meaning. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves 'backing SAP memory session status for a chat room', using a specific verb and resource. It distinguishes from sibling chat tools like 'sap_chat_read_all' or 'sap_chat_start_room' by focusing on session status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., 'sap_session_status' or other chat tools). The description lacks context about prerequisites or scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server