Skip to main content
Glama

binary-forensics

sourcemap_analyze

Audit a JavaScript SourceMap (.js.map) v3 JSON file to break down bundled byte attribution per source module and spot bloated dependencies.

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": "sourcemap_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoRaw SourceMap v3 JSON.
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only audit and hints at the report contents (byte attribution per module, bloat flags), but never states that the file is not modified, how malformed or non-v3 maps are handled, whether size limits apply, or how results are returned. Useful outcome context, but the safety and edge-case profile is unstated.

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

Conciseness5/5

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

A single front-loaded sentence in which every clause contributes: the input format, the analysis performed, and both outputs. There is no redundant wording or filler.

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?

For a two-parameter analysis tool with no output schema and no annotations, the description covers purpose and hints at outputs but omits input-mode selection between text and filePath, error behavior, and confirmation that the operation is read-only. Adequate to identify the tool, but not complete enough to guarantee correct invocation.

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 coverage is 50%: 'text' is documented as raw SourceMap v3 JSON, but 'filePath' is undocumented in both schema and description, and the description only weakly implies file input. Neither parameter is required, yet the description never explains whether text and filePath are alternatives or how to choose between them, nor what happens if both or neither are supplied.

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

Purpose5/5

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

States a specific verb (audit) on a specific resource (JavaScript SourceMap .js.map v3 JSON) and names both outcomes: per-source-module byte attribution and bloated dependency detection. This clearly distinguishes it from the format-inspection siblings like hexdump_inspect or binary_triage.

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?

The description gives no when-to-use or when-not-to-use guidance, and does not reference any alternative (e.g., hexdump_inspect for raw bytes). It also does not clarify when a user should reach for this versus generic binary triage, leaving routing to inference from the purpose alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources