Skip to main content
Glama
Sign In
perfonext-build-mcp

perfonext-build-mcp

by souvikdu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Shared Chunks

get_shared_chunks

Rank the heaviest shared chunks in a loaded Next.js build and show which routes depend on them to target bundle size reductions.

Instructions

Rank the heaviest shared chunks in a loaded Next.js build and show which routes depend on them.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many shared chunks to include. Defaults to 10.
buildIdNoBuild ID returned from load_build_stats. Omit to list loaded builds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden, and it clearly states the core behavior: ranking shared chunks and showing dependent routes. It would benefit from mentioning the no-buildId listing mode, but the primary behavioral contract is transparent and non-mutating.

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 sentence conveys action, scope, and expected result with no redundant phrasing. The key verb and object are front-loaded, making the tool's purpose immediately clear.

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 tool with two optional parameters and no output schema, the description plus schema covers how to invoke it: it names the prerequisite state, the result shape, and both parameters. A small gap is that the description's 'loaded build' framing does not acknowledge the omit-buildId mode, but the schema fills this in.

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 both limit and buildId already have meaningful descriptions in the schema. The description adds no parameter-specific information, so the baseline score of 3 is appropriate.

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?

The description opens with a specific action ('Rank'), targets a concrete resource ('heaviest shared chunks'), and states the derived output ('show which routes depend on them'). This is distinct from sibling tools like get_largest_routes, which targets routes rather than chunks, and explain_shared_chunks, which is about explanation rather than ranking.

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 phrase 'in a loaded Next.js build' implies that load_build_stats should be run first, which is useful context. However, the description never explicitly says when to choose this tool over explain_shared_chunks, get_largest_routes, or suggest_optimizations, and it leaves the omit-buildId behavior to the schema.

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