tslink

Overview Schema Source Related Servers Discussions Admin

Show a browser guest link

guest_show

Read-onlyIdempotent

Look up one browser guest grant by ID to return metadata, expiry, revocation status, and use counters; unknown IDs return not_found.

Instructions

Owner-only: look up one browser guest grant by ID and return its metadata, expiry, revocation status and use counters; unknown IDs return not_found. Use guest_show for one known grant; use guest_list to discover IDs. Read-only local state, with no remote API calls or bearer token recovery; create a new link with guest_create if needed. Does not verify live Funnel availability. Visitors need no OIDC or tailnet account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description	Default
`grant`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive/closed-world, and the description still adds substantial behavior: owner-only auth requirement, not_found on unknown IDs, no remote API calls, no bearer token recovery, no live Funnel verification, and that visitors need no OIDC or tailnet account. This goes well beyond the annotations.

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 owner-only constraint and the core action, and every clause adds a distinct fact (scope, error case, alternatives, limits). The multi-clause semicolon structure is dense but not padded; a slight reduction in length would improve scanability.

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 shape need not be spelled out, yet the description still summarizes what is returned. With annotations, error semantics, auth requirement, and adjacent tools all covered, an agent has everything needed to invoke this correctly.

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 0% for the single 'id' parameter. The description identifies it as a browser guest grant ID and defines the error case for unknown IDs, but adds no format, prefix, or ID-source detail (e.g., where to obtain the ID beyond guest_list). Baseline-minimal parameter meaning.

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 (look up) and resource (one browser guest grant by ID) plus the scope of the return (metadata, expiry, revocation status, use counters). It explicitly contrasts itself with the sibling guest_list, so an agent can route correctly without opening a 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?

Gives explicit when-to-use: guest_show for one known grant, guest_list to discover IDs, guest_create to make a new link. Prerequisites (owner-only) and a boundary condition (does not verify live Funnel availability) are stated outright.

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