tslink

Overview Schema Source Related Servers Discussions Admin

Detect local apps

apps_detect

Read-onlyIdempotent

Discover local listening TCP services via credential-free loopback HTTP fingerprints, returning confidence and registered services; use results to choose apps for private Tailscale HTTPS addresses.

Instructions

Discover local listening TCP services using credential-free, bounded loopback HTTP fingerprints. Never follows redirects or probes non-loopback addresses. Returns confidence and already registered services; does not verify authentication or health.

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": "apps_detect"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`matches`	Yes
`complete`	Yes
`warnings`	Yes
`listeners`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.5/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, and the description still adds substantial context: operations are credential-free and bounded, redirects are never followed, non-loopback addresses are never probed, and results exclude auth/health verification. That is above and beyond the structured hints.

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, zero filler. The core capability is front-loaded and each following clause adds a distinct boundary or output note.

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?

With an output schema present, return values need not be explained, yet the description still notes that confidence and already-registered services are returned. Safety profile, scope restrictions, and limits 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 no parameter surface for the description to clarify. Schema coverage is listed at 100%, leaving nothing to compensate for.

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 ('Discover local listening TCP services') plus the mechanism ('credential-free, bounded loopback HTTP fingerprints'). No sibling tool in the list does local service discovery, so the agent can select it unambiguously.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description bounds behavior clearly (no redirects, no non-loopback probes) but gives no explicit when-to-use framing or routing to alternatives such as 'health' or 'doctor' for verification tasks. Usage is implied rather than stated.

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