UniAffitti Room Finder

Read one UniAffitti conversation

get_my_conversation_messages

Read-onlyIdempotent

Load the recent messages for one authenticated UniAffitti conversation. This is a data-only tool intended to be called by the messages UI after the user selects a conversation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`messages_limit`	No
`conversation_id`	Yes	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"
+}

AddedSep 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the 'data-only' framing (no side effects) and the UI-driven invocation model, but says nothing about result ordering or what happens when messages_limit truncates the output.

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 tight sentences, front-loaded with the action and resource before the invocation context. No filler, though it is thin enough that a few more decisive details could have been added at no structural cost.

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

Completeness4/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 values need no explanation, and the read-only safety profile is covered by annotations. For a 2-parameter read tool the description is nearly complete, with the only meaningful gap being ordering/limit behavior for messages_limit.

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 50%: conversation_id is documented in the schema, while messages_limit carries only a default/min/max with no description. The phrase 'recent messages' hints at recency ordering but does not explain that messages_limit caps how many are returned, so the description does not fully compensate for the gap.

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 and resource: 'Load the recent messages for one authenticated UniAffitti conversation.' The 'one ... conversation' scoping implicitly separates it from the list_my_messages sibling, though that sibling is never named, so it stops short of explicit differentiation.

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

Usage Guidelines3/5

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

Gives a usage context ('intended to be called by the messages UI after the user selects a conversation'), which implies the trigger condition. It never states when not to use it or names the alternative for browsing conversations, so guidance is implied rather than explicit.

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?