Skip to main content
Glama
jigyasudham

veto

by jigyasudham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

veto_bundle_advisor

Read-only

Analyze webpack stats JSON to identify heaviest assets and duplicate packages, then suggest code-splitting and CDN externalization.

Instructions

Accepts a webpack-format stats JSON (webpack --json) → heaviest assets and modules and duplicated packages (computed), plus code-split and CDN-externalization suggestions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stats_fileYesAbsolute path to the bundle stats JSON file (webpack stats format).
project_dirNoOptional absolute path to the project root.
agent_responseNoPhase 2 response from the host AI (JSON). Pass this back when prompted by the server to complete the agentic loop.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.9.0
    • addedInput schema / properties / agent_response
      Added value: +{
+  "description": "Phase 2 response from the host AI (JSON). Pass this back when prompted by the server to complete the agentic loop.",
+  "type": "object"
+}
  2. First observedv2.7.1

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe, non-mutating read, so the bar is lower. The description adds that the figures are '(computed)' (deterministic analysis) and lists the output categories, but it omits the two-phase agentic loop (the agent_response round-trip) that the schema reveals and does not disclose any rate limits, file-size caveats, or failure modes.

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?

It is a single front-loaded sentence with no wasted clauses, and the input format is stated first. The arrow notation and the slightly run-on 'heaviest assets and modules and duplicated packages' list make it terser than ideal, keeping it out of the top tier.

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?

With no output schema, the description does cover the returned categories well. However, for a tool whose schema exposes a phase-2 agentic loop, the description never explains that the caller may be prompted to pass an agent_response back to complete processing, leaving a meaningful behavioral gap.

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 100%, so stats_file, project_dir, and agent_response are each documented in the schema. The description only gestures at the input format (webpack stats JSON) and adds no syntax or format detail beyond what the schema already supplies, so the baseline of 3 is appropriate.

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 and resource: it consumes webpack-format stats JSON and produces heaviest assets/modules, duplicated packages, and code-split/CDN suggestions. This clearly separates it from the advisor siblings (dep_advisor, sre_advisor), though it never names a sibling explicitly, so it lands just shy of the top mark.

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?

Usage is only implied: an agent can infer you call it when you have a webpack `--json` stats file and want bundle optimizations. There is no explicit when/when-not guidance or mention of how it relates to veto_dep_advisor or other analysis tools.

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