Skip to main content
Glama

Reconcile Javascript Runtime

reconcile_javascript_runtime
Idempotent

Reconciles verified static JavaScript application graphs with CDP, V8, or Electron runtime observations while keeping target, script, frame, worker ambiguity and source-map authority explicit.

Instructions

Reconcile verified static JavaScript application graphs with existing passive web/Electron CDP, passive V8 Inspector, or provider-owned active Electron Evidence. Active Electron captures contribute an explicitly partial target-only runtime record; they never invent renderer scripts, frames, workers, or execution claims. Exact captured-source digests take priority over caller-declared file/URL mappings; target, frame, script, and worker ambiguity remains explicit, and source-map authority stays separate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "static_layers": "<static_layers>",
      "runtime_observations": "<runtime_observations>"
    },
    "name": "reconcile_javascript_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
static_layersYes
runtime_observationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description adds meaningful behavior: active Electron captures are explicitly partial and target-only, never invent renderer scripts/frames/workers/execution claims, and exact captured-source digests take priority over caller mappings. It also keeps ambiguity and source-map authority explicit. It does not clarify side effects despite readOnlyHint=false, which keeps it short of a 5.

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?

The description is front-loaded with purpose and then adds behavioral constraints in three dense sentences. Every sentence carries relevant information, though the phrasing is jargon-heavy and tightly packed for a complex reconciliation tool.

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

Completeness3/5

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

The tool is complex, has no output schema, and its top-level parameters have 0% schema description coverage. The description covers important behavioral constraints but does not describe the expected return values or summarize the input structure, so it is minimally adequate rather than complete.

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

Parameters3/5

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

Schema description coverage is 0% for the two required top-level parameters, so the description must compensate. It adds useful semantics for runtime mapping priority, ambiguity, and source-map authority, but it does not explain the structure or required contents of static_layers and runtime_observations, leaving the large nested schema to carry most parameter meaning.

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?

The description states a specific verb ('Reconcile') and resource ('verified static JavaScript application graphs' with runtime evidence), making the core purpose clear. It distinguishes passive web/Electron CDP, passive V8 Inspector, and provider-owned active Electron Evidence, though it does not explicitly name sibling tools or state which sibling to use instead.

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?

The description implies when the tool applies: when reconciling verified static graphs with existing passive or provider-owned active runtime evidence. It does not explicitly state when not to use it or compare it with alternatives such as observe_javascript_runtime or correlate_static_and_runtime, so usage guidance remains implicit.

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

Deploy Server

Other Tools