UniAffitti Room Finder

Read my messages

list_my_messages

Read-onlyIdempotent

Read the authenticated user’s UniAffitti conversations from the same chat used by the web app. Without a conversation_id return fast conversation summaries and last-message previews; with one load the complete recent messages for that conversation.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`unread_only`	No
`messages_limit`	No
`conversation_id`	No	Optional Firebase conversation/thread id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	Yes
`has_more`	Yes
`unread_only`	Yes
`conversations`	Yes
`messages_limit`	Yes
`conversation_id`	Yes
`unread_messages`	Yes
`total_conversations`	Yes
`returned_conversations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "conversation_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "conversations": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "conversation_id": {
+            "type": "string"
+          },
+          "last_message": {
+            "type": "string"
+          },
+          "last_message_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "messages": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "created_at": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "is_from_me": {
+                  "type": "boolean"
+                },
+                "message_type": {
+                  "type": "string"
+                },
+                "sender_name": {
+                  "type": "string"
+                },
+                "text": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "sender_name",
+                "is_from_me",
+                "message_type",
+                "text",
+                "created_at"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "messages_loaded": {
+            "type": "boolean"
+          },
+          "other_participant": {
+            "additionalProperties": false,
+            "properties": {
+              "name": {
+                "type": "string"
+              },
+              "role": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "role",
+              "name"
+            ],
+            "type": "object"
+          },
+          "room_cover_url": {
+            "type": "string"
+          },
+          "room_title": {
+            "type": "string"
+          },
+          "unread_count": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "conversation_id",
+          "room_title",
+          "room_cover_url",
+          "other_participant",
+          "last_message",
+          "last_message_at",
+          "unread_count",
+          "messages_loaded",
+          "messages"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "limit": {
+      "type": "integer"
+    },
+    "messages_limit": {
+      "type": "integer"
+    },
+    "returned_conversations": {
+      "type": "integer"
+    },
+    "total_conversations": {
+      "type": "integer"
+    },
+    "unread_messages": {
+      "type": "integer"
+    },
+    "unread_only": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "conversations",
+    "total_conversations",
+    "returned_conversations",
+    "unread_messages",
+    "unread_only",
+    "limit",
+    "messages_limit",
+    "has_more",
+    "conversation_id"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 31, 2026
- changedInput schema / properties / limit / default
```
Previous value: -20New value: +12
```
AddedAug 31, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful mode context ('fast conversation summaries' vs 'complete recent messages' and web-app parity), but does not address truncation behavior, auth failure, or rate limits.

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?

Two compact sentences with the dual-mode distinction front-loaded and no padding. It is dense but every clause carries information, though the clause ordering mixes scope and mode slightly.

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

Completeness3/5

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

An output schema exists, so return-value detail is not required. The description covers the mode split but leaves the limit/messages_limit and unread_only semantics unexplained, which is a meaningful gap for a 4-parameter list tool.

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

Parameters2/5

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

Schema description coverage is only 25%; only conversation_id is documented in the schema. The description does not explain limit versus messages_limit (the distinction an agent most needs), nor unread_only, so three parameters remain ambiguous.

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?

States a specific verb (read) and resource (authenticated user's UniAffitti conversations) and clarifies the dual-mode behavior: summaries without conversation_id, full messages with it. It does not, however, distinguish itself from the sibling get_my_conversation_messages, which appears to cover the same with-id case.

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?

Clearly explains the two calling modes and what each returns, so an agent knows which parameters select which behavior. It stops short of naming an alternative tool or stating exclusions, leaving the overlap with get_my_conversation_messages unresolved.

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

All UniAffitti Room Finder 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?