volume_snapshot_cr_getRetrieve a single CRD-backed snapshot for a specific volume to inspect its configuration or status. Use this when you need detailed snapshot information without listing all snapshots.
Get one CRD-backed snapshot for a volume. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/setup-a-snapshot/
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| snapshotName | Yes |
Changes observed during successful MCP inspections.
v0.1.6Does 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 only states that the tool gets a CRD-backed snapshot; it does not describe read-only behavior, what happens when the snapshot is not found, required permissions, or what is actually returned. The docs link points to setup steps, not tool behavior.
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, front-loaded sentence that states the verb and object immediately. The documentation link adds context without bloating the description, and 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 tool with two required parameters, no output schema, and no annotations, this description is under-specified. It omits parameter semantics, return value shape, not-found behavior, and any routing guidance among sibling snapshot tools. The docs link provides some help but does not make the description complete enough on its own.
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 description coverage is 0%, and the description does not map the required parameters name and snapshotName to their roles beyond 'for a volume.' An agent must infer that 'name' is likely the volume name and 'snapshotName' is the snapshot name; the description adds almost no parameter-level meaning.
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 clearly identifies the resource as a CRD-backed snapshot for a volume. The 'CRD-backed' qualifier distinguishes it from sibling getters like volume_snapshot_get or snapshot_get, and 'one' makes the singular nature of the operation clear.
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?
There is no explicit guidance about when to use this tool versus volume_snapshot_cr_list, volume_snapshot_get, or snapshot_get. Usage must be inferred from the tool name and the phrase 'get one'; no alternatives, exclusions, prerequisites, or conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.