Mine archived URLs/params/endpoints from a Wayback/CDX export
Single tool 'waybackrecon_scan' has a basic description (79 chars) but critically lacks parameter descriptions. The input schema defines 'target' as a string with a description, but the tool description itself is vague about what 'target' should be (path? URL? file?). No output schema is documented. The tool name uses verb_noun pattern correctly, but the implementation is minimal and lacks error handling guidance, validation rules, or recovery paths. No pagination, no structured output documentation, no security considerations.
Mine archived URLs/params/endpoints from a Wayback/CDX export. Returns JSON findings.
Parameter 'target' lacks actionable description. Does it accept a file path, URL, directory, or Wayback CDX export format? LLM cannot infer valid input.
No output schema documented. Tool returns JSON but structure is not specified. LLM cannot plan downstream operations or extract fields reliably.
No error handling or recovery guidance. Tool description does not explain failure modes (invalid path, malformed export, timeout) or what LLM should do next.
Tool description is generic and lacks context. 'Mine archived URLs/params/endpoints from a Wayback/CDX export' does not explain when to use this vs other tools, what prerequisites exist, or what 'findings' means.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
No input validation rules documented. Description should specify: file format (CDX JSON?), path constraints, size limits, timeout behavior, and example valid inputs.