Skip to main content
Glama

Threshold

by rentals.threshold
OverviewDiscussionsAdmin

Read messages with the host

get_messages
Read-only

The conversation between the guest and the host about a booking, oldest first (including the guest's note with the request and the host's note when accepting or declining). Use it to relay the host's replies. Pass guest_email (the email the booking was made with) unless you connect with an agent token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
booking_idYesThe booking's id, from request_booking (starts with bkg_).
guest_emailNoThe email the booking was made with. Needed unless you connect with an agent token.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / booking_id / description
      Added value: +"The booking's id, from request_booking (starts with bkg_)."
    • addedInput schema / properties / guest_email / description
      Added value: +"The email the booking was made with. Needed unless you connect with an agent token."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The conversation with the host, oldest first.",
+  "properties": {
+    "messages": {
+      "items": {
+        "additionalProperties": true,
+        "description": "One message.",
+        "properties": {
+          "body": {
+            "type": "string"
+          },
+          "from": {
+            "description": "guest or host",
+            "type": "string"
+          },
+          "sent_at": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: the chronological ordering, the inclusion of the guest's request note and the host's accept/decline note, and the auth shortcut for agent tokens.

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 resource and its ordering, then the intended use, then the parameter caveat. Three tight clauses with no padding, though the guest_email instruction duplicates the schema wording.

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-format detail is unnecessary. The description covers scope, ordering, and the auth requirement, which is enough to call the tool correctly; only an explicit pointer to the sibling write tool is missing.

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%, so both parameters are already documented with their formats and the bkg_ prefix. The description's note about guest_email largely restates the schema's 'Needed unless you connect with an agent token', adding no new syntax or format detail.

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 — reading the guest/host conversation about a booking — and even specifies ordering ('oldest first') and the included notes. An agent can tell this apart from send_message/ask_host (which write) and get_booking (which returns booking data, not the thread).

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?

'Use it to relay the host's replies' gives a clear context for invocation, and the guest_email/agent-token note signals the auth conditions. It stops short of explicitly naming send_message as the counterpart for replying, so it is context rather than full when/when-not routing.

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

All Threshold toolsInspect
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