Skip to main content
Glama
Sign In

Snapstay

by ai.snapstay
OverviewDiscussionsAdmin

Find guests by name or email using full-text search

guests.search
Read-onlyIdempotent

Find guests by name or email using full-text search. Use guests.list for partial matching or to browse all guests. Returns up to 100 guest IDs and names per page. Set page to the returned page.next to continue. A next value of 0 marks the last page.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Omit for the first page.
queryYesFull-text search terms for a name or email, up to 200 characters. Use guests.list to match part of a name or email.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search text, up to 200 characters."New value: +"Full-text search terms for a name or email, up to 200 characters. Use guests.list to match part of a name or email."
  2. Changed7 schema fields changed
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page number, starting at 1. Omit for the first page.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / query / description
      Added value: +"Search text, up to 200 characters."
    • addedOutput schema / properties / result / additionalProperties
      Added value: +false
    • removedOutput schema / properties / result / items
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "familyName": {
-      "type": "string"
-    },
-    "givenName": {
-      "type": "string"
-    },
-    "id": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "id",
-    "givenName",
-    "familyName"
-  ],
-  "type": "object"
-}
    • addedOutput schema / properties / result / properties
      Added value: +{
+  "items": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "familyName": {
+          "type": "string"
+        },
+        "givenName": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "givenName",
+        "familyName"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "page": {
+    "additionalProperties": false,
+    "properties": {
+      "count": {
+        "type": "number"
+      },
+      "next": {
+        "type": "number"
+      },
+      "number": {
+        "type": "number"
+      },
+      "previous": {
+        "type": "number"
+      },
+      "size": {
+        "type": "number"
+      },
+      "total": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "size",
+      "count",
+      "number",
+      "total",
+      "next",
+      "previous"
+    ],
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / result / required
      Added value: +[
+  "items"
+]
    • changedOutput schema / properties / result / type
      Previous value: -"array"New value: +"object"
  3. First observed

TDQS

A4.7/5.0
Behavior4/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 useful behavior the annotations don't: a 100-result page cap, the page.next continuation pattern, and the next=0 terminal marker. It stops short of describing result ordering or match ranking, which would matter for a search tool.

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

Conciseness5/5

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

Four tight sentences with zero waste; purpose and alternative routing are front-loaded before pagination mechanics. Every sentence carries distinct information.

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?

An output schema exists, so return values needn't be restated, and the description still covers the two things an agent must know to iterate results correctly. Nothing needed to invoke it properly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are already documented. The description still adds meaning beyond the schema by explaining that 'page' should be set to the returned page.next value and that next=0 signals the last page, which is operational guidance the schema cannot express.

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 ('Find'), resource ('guests'), and scope ('full-text search by name or email'), which distinguishes it from guests.list by matching mode. An agent can select it without inspecting 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 Guidelines5/5

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

Explicitly names the alternative ('Use guests.list for partial matching or to browse all guests') along with the condition that selects it. Pagination continuation is also spelled out, leaving nothing to inference.

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

All Snapstay 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