feat(javascript): return a retained summary view on request (#1568)
analyze_javascript_application returns the complete application graph inline, which repeats tens of kilobytes even for a few source lines and exceeds the default 10 MiB MCP frame for a 300-function source file. The new optional detail input keeps complete delivery by default. With detail "summary" the server records the complete analysis Evidence in the session and returns its inspect_analysis_view summary, whose parent_evidence_id lets callers page modules, select items, or pass the retained reference to application workflows. A server without Evidence retention refuses summary detail with capability_unavailable rather than returning a summary whose analysis cannot be reached. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
649661dc8b
commit
c19e15a2b3
@@ -318,6 +318,13 @@ Ordinary responses keep their existing complete result contract.
|
||||
|
||||
## Retained application Evidence inputs
|
||||
|
||||
`analyze_javascript_application` accepts `detail`: `complete` (default) returns
|
||||
the complete analysis Evidence; `summary` records that complete Evidence in the
|
||||
session and returns the derived `inspect_analysis_view` summary Evidence
|
||||
instead. Its `normalized_result.parent_evidence_id` and `evidence_links` name
|
||||
the retained analysis, so later views and application workflows read it without
|
||||
repeating analysis or moving the complete graph through the response.
|
||||
|
||||
`inspect_analysis_view` projects a caller-selected view of already completed
|
||||
`inspect_binary_layout`, `analyze_javascript_application`, or `analyze_function`
|
||||
Evidence. Native views select procedure, pseudocode, assembly, basic blocks,
|
||||
|
||||
Reference in New Issue
Block a user