Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Get network flow logs

tailscale_get_network_flow_logs
Read-onlyIdempotent

Retrieve network traffic flow logs to inspect connections between devices, including source/destination nodes, timestamps, and metadata for security monitoring and connectivity debugging.

Instructions

Get network traffic flow logs showing connections between devices. Shows source/destination nodes, timestamps, and traffic metadata -- useful for security monitoring and debugging connectivity.

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": {
      "start": "<start>"
    },
    "name": "tailscale_get_network_flow_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd time in RFC3339 format. Optional: when omitted the tool sends the current time, which Tailscale's API requires.
startYesStart time in RFC3339 format (e.g. '2026-04-01T00:00:00Z'). Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.21.0
    • changedInput schema / properties / end / description
      Previous value: -"End time in RFC3339 format. Defaults to now."New value: +"End time in RFC3339 format. Optional: when omitted the tool sends the current time, which Tailscale's API requires."
  2. First observedv0.13.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered; the description adds the returned field categories. It omits operationally important behavior such as result volume, pagination or truncation, retention limits on flow logs, and whether flow logging must be enabled on the tailnet first. With annotation coverage present, this partial addition lands at adequate.

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?

Two sentences, front-loaded with the resource and followed by concrete return content. No filler, though the second sentence's 'traffic metadata' is vague enough to be slightly wasted space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with no output schema and strong annotations, the description covers purpose and rough shape of results. It is still missing prerequisites (flow logs enabled), possible truncation of large result sets, and any indication of what the agent should do if the window returns nothing.

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 100% and the schema already explains the RFC3339 formats and the default-current-time behavior for 'end'. The description says nothing about the time window parameters or any limits on range width, so it adds no meaning beyond the schema — the baseline 3 for full coverage.

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?

States a specific verb and resource ('Get network traffic flow logs') and clarifies the content is connections between devices with source/destination nodes and timestamps, which separates it from tailscale_get_audit_log. It does not explicitly name or contrast with that sibling, so an agent must infer the distinction.

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 phrase 'useful for security monitoring and debugging connectivity' hints at when to reach for it, but there is no explicit when-not guidance and no reference to alternative tools such as tailscale_get_audit_log or the log stream config tools. Usage is implied rather than prescribed.

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

Deploy Server

Other Tools