tailscale_get_log_stream_configFetch log streaming configuration for audit or network flow logs in Tailscale. Use to verify current settings before modifying them.
Get the log streaming configuration for a specific log type.
| Name | Required | Description | Default |
|---|---|---|---|
| logType | Yes | The log type: 'configuration' for audit logs, 'network' for network flow logs |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that (no auth requirements, rate limits, or error behavior), which is acceptable but minimal for a read tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence with the resource and scope front-loaded. Nothing extraneous, though it is on the terse side.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read with annotations covering safety and no output schema required, the description is adequate but thin — it leaves all context to the schema and annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the enum (configuration/network) is fully documented in the schema itself. The description only restates that the config is keyed by log type, adding no meaning beyond the schema — baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (log streaming configuration) with a scoping qualifier (for a specific log type). This distinguishes it from list_log_stream_configs and get_log_stream_status, though it doesn't name those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'for a specific log type' implicitly differentiates a single-config read from the list_ sibling, but there is no explicit when-to-use guidance, no exclusions, and no named alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.