Fetch device information by its Tachyon GUID to identify and manage a specific device within a 1E DEX tenant. Provides direct access to device details for targeted operations.
Get a single device by its Tachyon GUID (the unique identifier assigned by the 1E agent).
| Name | Required | Description | Default |
|---|---|---|---|
| guid | Yes | Tachyon GUID of the device |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral disclosure burden. It clarifies that the Tachyon GUID is assigned by the 1E agent, which is useful context, but it does not disclose what happens when no device is found, whether the response is a full device object, or any error behavior. For a simple read-only getter, this is acceptable though not rich.
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, front-loaded sentence contains the action, resource, and key semantic context with zero filler. Every word earns its place.
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 single-parameter read operation with no output schema, the description is largely complete. It states what the tool does and what identifier it uses. Minor gaps, such as not-found behavior and response shape, are low-risk for this simple getter.
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%, so the baseline is 3. The description adds meaning beyond the schema by explaining that the Tachyon GUID is the unique identifier assigned by the 1E agent, giving an agent useful context about the parameter's source and significance.
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 states a specific verb ('Get'), a specific resource ('a single device'), and the exact lookup key ('Tachyon GUID'), clearly distinguishing this tool from siblings such as devices_get_by_fqdn and devices_search. The parenthetical explanation of what a Tachyon GUID is adds helpful clarity.
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 when a Tachyon GUID is available, but it provides no explicit guidance about when to use this tool versus alternatives like devices_get_by_fqdn, devices_list, or devices_search. No exclusions 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.