Retrieve log streaming configuration for configuration audit logs or network flow logs in your Tailscale tailnet. Specify the log type to get its current streaming settings.
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, idempotentHint, and destructiveHint, so the description adds no behavioral context beyond that. It does not discuss return format, error scenarios, or authentication needs, which would be useful given the lack of an output schema.
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?
Single sentence that is perfectly concise and front-loaded with the action and resource. No extraneous words.
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 read-only tool with one parameter and rich annotations, the description covers the essential purpose. However, it could mention that the configuration is retrieved (e.g., 'returns the current log stream configuration for the specified log type') to slightly improve completeness.
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%, with the parameter logType fully described via an enum and descriptions. The description does not add extra meaning; baseline 3 is appropriate.
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?
The description uses a specific verb 'Get' and identifies the resource 'log streaming configuration' with a constraint 'for a specific log type', clearly distinguishing it from sibling tools like tailscale_list_log_stream_configs (which lists all) and tailscale_set_log_stream_config (which modifies).
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 description implies usage for retrieving a single log type configuration but does not explicitly state when to use it vs. listing all configurations (tailscale_list_log_stream_configs) or when not to use it. No prerequisites or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.