Skip to main content
Glama

carve_residual_usn

Carve residual USN_RECORD_V2 structures from a region to independently recover change-journal records when rotated $J data is missing or unusable.

Instructions

Carve residual USN_RECORD_V2 structures from a region (rotated-$J fallback / independent recovery).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "carve_residual_usn"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoauto
max_recordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full behavioral burden. 'Residual' and 'recovery' hint at a read-only carving operation over stale records, but it never states whether the operation is read-only, what it returns, how partial/garbage records are handled, or failure behavior for a bad region.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is compact and does not waste words, though the density of bare jargon (USN_RECORD_V2, rotated-$J) limits immediate comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A specialized forensic recovery tool with no annotations, no output schema, and zero schema description coverage gets only one sentence. Critical details—cap behavior of max_records, meaning of the auto region, and result shape—are absent, leaving the agent underinformed for a non-trivial carve operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and does not. It implies 'region' selects the source area but never explains its accepted forms or what the default 'auto' resolves to, and 'max_records' (default 64) is never mentioned at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Carve residual USN_RECORD_V2 structures from a region.' The parenthetical framing ('rotated-$J fallback / independent recovery') signals the recovery purpose and implicitly distinguishes it from a normal USN enumeration path, though it names no sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'rotated-$J fallback' implies the condition under which this tool is preferred (when the standard $J has been rotated), but the guidance is oblique jargon rather than an explicit when-to-use/when-not statement, and no alternative tool is named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.