Skip to main content
Glama

List Javascript Runtime Targets

list_javascript_runtime_targets
Idempotent

Lists eligible Node/Electron V8 Inspector targets from a literal-loopback endpoint without attaching, preserving unverified discovery URLs as unresolved so you can identify reachable runtimes.

Instructions

List every eligible Node/Electron V8 Inspector target from an explicit literal-loopback endpoint. Node discovery file locations that cannot be verified are preserved as unresolved reported URLs; they do not prove filesystem identity. Listing does not attach to targets.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "inspector_endpoint": "http://127.0.0.1:9229"
    },
    "name": "list_javascript_runtime_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
inspector_endpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond annotations, it discloses that listing does not attach to targets and that unverifiable Node discovery file locations are reported as unresolved URLs rather than proven filesystem identities. That is useful behavioral context; the readOnlyHint=false annotation is not directly contradicted because 'does not attach' is narrower than a read-only claim.

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?

Three sentences, front-loaded with the action and scope; the unresolved-URL caveat is dense but relevant. No obvious filler.

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

Completeness4/5

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

For a one-parameter listing tool with no output schema, the description covers scope, non-attachment, and unresolved URL semantics. It still omits return shape/pagination details, but annotations and schema carry enough for correct invocation.

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 coverage is 0%, so the description must carry parameter meaning. It adds the important constraint that the endpoint must be an explicit literal-loopback endpoint, but it does not name inspector_endpoint or explain accepted URL forms beyond the schema example.

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 uses a specific verb ('List') and resource ('Node/Electron V8 Inspector target') and scopes it to an explicit literal-loopback endpoint. It does not explicitly differentiate from sibling list_electron_targets or list_browser_targets, so it is clear but not fully sibling-routing.

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

Usage Guidelines2/5

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

It implies use for enumerating eligible targets from a loopback endpoint, but gives no when-to-use/when-not guidance and does not name observe_javascript_runtime or other alternatives. An agent must infer the selection context.

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