tslink

Overview Schema Source Related Servers Discussions Admin

Create a browser guest link

guest_create

Create a time-limited browser guest grant for a proxy app, configuring its guest gate and public Funnel exposure. Returns grant metadata; bearer link only if print_link is true.

Instructions

Owner-only: create a time-limited browser guest grant for one proxy app and configure its guest gate and enable public Funnel exposure (applied by the daemon). Returns grant metadata, a recipient message and configured edge state; the bearer link is hidden unless print_link is true and is only available at creation. Use guest_create for a new link; guest_show cannot recover an existing token. Requires public acknowledgement when first enabling the guest gate. No OIDC or tailnet account is required for the visitor. Makes no remote API calls; check status separately for live Funnel availability.

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": {
      "app": "<app>",
      "for": "<for>"
    },
    "name": "guest_create"
  }
}

Input Schema

Name	Required	Description
`app`	Yes
`for`	Yes	Relative lifetime (descending unique units w,d,h,m,s,ms,us,ns) or until <RFC3339\|YYYY-MM-DD\|YYYY-MM-DDTHH:MM>. Local unless offset given; DST gaps/folds require an offset. Minimum 1h. Presets: 1h, 8h, 24h, 3d, 7d. Default 24h; guest/public maximum defaults to 7d, configurable in durations.public_max. Never refused. Omission on add preserves an existing deadline.
`pin`	No	Optional secret 6..64 digit PIN; never log it.
`label`	No
`public`	No
`print_link`	No	Explicitly request the bearer link once; default output is masked.

Output Schema

Name	Required	Description	Default
`link`	Yes
`grant`	Yes
`message`	Yes
`edge_state`	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 cover basic safety flags (readOnly false, destructive false), and the description adds substantial context beyond them: owner-only restriction, the bearer link being hidden unless print_link is true and only retrievable at creation, the public-acknowledgement requirement, no result from remote API calls, and visitor auth needs.

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?

It is a dense single block but front-loads the owner-only scope and core action before secondary caveats. Every clause carries information, though the sentence packing slightly reduces scannability.

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?

Although an output schema exists, the description still summarizes the return (grant metadata, recipient message, configured edge state) and covers auth prerequisites, the visitor exemption, and the live-Funnel caveat, leaving nothing critical for correct invocation unstated.

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 50%, so the description must compensate, and it partially does by explaining print_link behavior and the public/Funnel exposure. However, it adds little meaning for app, pin, or label, leaving half the parameters to the schema alone.

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?

The description states a specific verb and resource: creating a time-limited browser guest grant for one proxy app, including gate configuration and Funnel exposure. It also explicitly distinguishes itself from the sibling guest_show, so an agent can route correctly without opening schemas.

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?

It names the alternative explicitly ('Use guest_create for a new link; guest_show cannot recover an existing token') and gives the condition that selects each. It further directs the agent to 'check status separately for live Funnel availability', providing when-to-use and where-not-to-look guidance.

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