Tessryx

List visitors

list_visitors

Read-onlyIdempotent

List this workspace's visitors: people who accepted an invite to its private pages (the default), or with pending=true the invites not accepted yet. Paged; pass next_page_token back as page_token for more. Visitors are named by email address; pass it to remove_visitor.

Input Schema

Name	Required	Description
`pending`	No	true lists invites not yet accepted; false or omitted lists visitors who accepted.
`page_size`	No	At most this many per page (default 50, at most 100).
`page_token`	No	next_page_token from the previous page.

Output Schema

Name	Required	Description	Default
`invites`	Yes
`pending`	Yes
`visitors`	Yes
`next_page_token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 6, 2026

addedOutput schema / properties / invites / items / properties / all_sites
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / invites / items / properties / sites

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "app": {
+        "type": "string"
+      },
+      "folder": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedOutput schema / properties / invites / items / required

Previous value: -[
-  "email",
-  "invited_by_user_id",
-  "created_at"
-]New value: +[
+  "email",
+  "invited_by_user_id",
+  "created_at",
+  "all_sites",
+  "sites"
+]

addedOutput schema / properties / visitors / items / properties / all_sites
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / visitors / items / properties / sites

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "app": {
+        "type": "string"
+      },
+      "folder": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedOutput schema / properties / visitors / items / required

Previous value: -[
-  "email",
-  "invited_by_user_id",
-  "accepted_at"
-]New value: +[
+  "email",
+  "invited_by_user_id",
+  "accepted_at",
+  "all_sites",
+  "sites"
+]

Changed2 schema fields changedNov 5, 2026

removedOutput schema / properties / visitors / items / properties / user_id
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / visitors / items / required

Previous value: -[
-  "user_id",
-  "email",
-  "invited_by_user_id",
-  "accepted_at"
-]New value: +[
+  "email",
+  "invited_by_user_id",
+  "accepted_at"
+]

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the result is paged, the returned next_page_token must be fed back as page_token, and visitors are identified by email — none of which the annotations convey.

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?

Three short sentences, zero filler, with the core definition and the default mode front-loaded before the optional mode and pagination mechanics.

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 three-optional-parameter read tool with an output schema and full annotation coverage, the description covers scope, mode selection, pagination, and the natural next action. Nothing an agent needs in order to call it correctly 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 coverage is 100% and each parameter already has a description, so the schema carries the parameter burden. The description restates the pending semantics and the page_token round-trip rather than adding syntax, bounds, or defaults beyond what the schema provides.

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?

The description gives a specific verb and resource ("List this workspace's visitors") and defines the population precisely as people who accepted an invite to private pages, with pending invites as the alternate mode. It does not explicitly differentiate from the sibling list_members, which is the most likely confusion given both list people in a workspace.

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?

It states the default mode (accepted visitors) and the exact switch for the other mode (pending=true), and it names remove_visitor as the follow-on action after obtaining a visitor's email. It stops short of saying when a caller should choose visitors over members.

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

All Tessryx 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?