tslink

Overview Schema Source Related Servers Discussions Admin

List browser guest links

guest_list

Read-onlyIdempotent

Read all browser guest grants from local state, including expiry, revocation status, and use counters, to find grant IDs across apps. Returns read-only grant data without secrets.

Instructions

Owner-only: read all browser guest grants from local state, including expiry, revocation status and use counters. Returns a grants array without bearer tokens or secret hashes. Use guest_list to find grant IDs across apps; use guest_show to inspect one known ID. Read-only, with no remote API calls; does not verify live Funnel availability. Visitors need no OIDC or tailnet account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "guest_list"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`grants`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, but the description adds substantive context beyond them: owner-only authorization, reading from local state, that the grants array excludes bearer tokens and secret hashes, that no remote API calls occur, and that it does not verify live Funnel availability. It also notes visitors need no OIDC or tailnet account.

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 tight sentences with the owner-only constraint and the read scope front-loaded, followed by sibling routing and behavioral caveats. Every clause carries information an agent needs.

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-value detail is optional, yet the description still notes the shape and the deliberate omission of secrets. Authorization, data source, side-effect profile and the non-verification caveat are all covered.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. No parameter-level meaning is added or needed.

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 ('read all browser guest grants from local state') and enumerates what is included: expiry, revocation status and use counters. It also names the sibling it is not, guest_show, so an agent can route without opening either 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 routes usage: 'Use guest_list to find grant IDs across apps; use guest_show to inspect one known ID.' This is a clear when-to-use plus a named alternative with the condition that selects it.

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