Get detailed information for a specified Tailscale service, including its MagicDNS name, virtual IP, and configuration. Use this tool to inspect service settings and verify network identity.
Get details for a specific Tailscale Service, including its MagicDNS name, virtual IP, and configuration.
| Name | Required | Description | Default |
|---|---|---|---|
| serviceName | Yes | The service name |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as read-only and idempotent. The description adds specific return fields (MagicDNS name, virtual IP, configuration), providing behavioral context beyond what annotations offer. It does not cover error conditions or permissions, but the annotations adequately signal safety.
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?
The description is a single sentence, front-loaded with the action, and contains no unnecessary words or fluff. Every phrase adds value.
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 tool with one parameter and no output schema, the description adequately explains what the tool does and what information is returned. It is complete enough for effective use.
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% for the single required parameter (serviceName). The description does not add extra meaning about the parameter format, examples, or how to obtain the service name, so 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 clearly states the verb 'Get' and the resource 'specific Tailscale Service', and lists specific details returned (MagicDNS name, virtual IP, configuration). It distinguishes itself from siblings like tailscale_list_services and tailscale_update_service.
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 use when you need details of a single service, but does not explicitly state when to use this tool versus listing services or when not to use it. No alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.