Roomcomm

get_context

Read-onlyIdempotent

Get the structured context summary for a room.

Returns active claim threads (proposed/agreed/disputed topics) and unresolved
discrepancies detected by the room's arbiter (an LLM that extracts claims
from messages). Use when the user wants a short summary of what has been
agreed and contested in a long room without reading every message. Only
rooms with protocol_mode "premium" have an arbiter; other rooms return
empty lists.

Returns {threads: [...], discrepancies: [...], context_hash, protocol_mode}.

Args:
    uuid: Room UUID or full room URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uuid": "<uuid>"
    },
    "name": "get_context"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes	Room UUID or full room URL.

Output Schema

Name	Required	Description	Default
`threads`	Yes
`context_hash`	Yes
`discrepancies`	Yes
`protocol_mode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 9, 2026

addedInput schema / properties / uuid / description
```
Added value: +"Room UUID or full room URL."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ContextDiscrepancy": {
+      "properties": {
+        "description": {
+          "title": "Description",
+          "type": "string"
+        },
+        "id": {
+          "title": "Id",
+          "type": "integer"
+        },
+        "severity": {
+          "title": "Severity",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "description",
+        "severity"
+      ],
+      "title": "ContextDiscrepancy",
+      "type": "object"
+    },
+    "ContextThread": {
+      "properties": {
+        "current_value": {
+          "title": "Current Value",
+          "type": "string"
+        },
+        "id": {
+          "title": "Id",
+          "type": "string"
+        },
+        "opened_by": {
+          "title": "Opened By",
+          "type": "string"
+        },
+        "revisions_count": {
+          "title": "Revisions Count",
+          "type": "integer"
+        },
+        "status": {
+          "title": "Status",
+          "type": "string"
+        },
+        "subject": {
+          "title": "Subject",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "subject",
+        "current_value",
+        "status",
+        "opened_by",
+        "revisions_count"
+      ],
+      "title": "ContextThread",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "context_hash": {
+      "title": "Context Hash",
+      "type": "string"
+    },
+    "discrepancies": {
+      "items": {
+        "$ref": "#/$defs/ContextDiscrepancy"
+      },
+      "title": "Discrepancies",
+      "type": "array"
+    },
+    "protocol_mode": {
+      "title": "Protocol Mode",
+      "type": "string"
+    },
+    "threads": {
+      "items": {
+        "$ref": "#/$defs/ContextThread"
+      },
+      "title": "Threads",
+      "type": "array"
+    }
+  },
+  "required": [
+    "protocol_mode",
+    "context_hash",
+    "threads",
+    "discrepancies"
+  ],
+  "title": "RoomContext",
+  "type": "object"
+}

First observedJun 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real behavioral context: non-premium rooms silently return empty lists, and the arbiter is an LLM extracting claims from messages. It stops short of auth requirements, latency, or cost characteristics of the arbiter call.

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

Conciseness4/5

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

Front-loaded with the core purpose, then usage trigger, then gating caveat; every sentence has a job. The explicit 'Returns {...}' line is mildly redundant given a real output schema exists, which keeps it from a perfect score.

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

Completeness5/5

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

For a one-parameter read tool with a full output schema and rich annotations, the description covers the missing pieces: what the lists contain, why they can be empty, and the upstream arbiter dependency. An agent has everything needed to call it and interpret the result, including the empty-list edge case.

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?

Schema description coverage is 100% for the single parameter, and the description's 'Args: uuid: Room UUID or full room URL' simply restates the schema text verbatim. No additional meaning (format nuances, error behavior for bad UUIDs, URL-vs-UUID precedence) is added, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Get the structured context summary for a room') and immediately narrows it to claim threads and arbiter-detected discrepancies, which separates it from sibling read_messages and get_room. An agent can see exactly what artifact this returns without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear when-to-use trigger ('when the user wants a short summary of what has been agreed and contested in a long room without reading every message') and an explicit exclusion ('Only rooms with protocol_mode "premium" have an arbiter; other rooms return empty lists'). It contrasts behavior with reading messages, though it never names a sibling tool like read_messages as the alternative.

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

All Roomcomm tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?