GitHub Next.js Optimizer MCP Server

analizar_repositorio

Analyze a GitHub repository to get optimization recommendations for Next.js and React projects, covering architecture, SOLID principles, performance patterns, and coding practices.

Instructions

Analiza un repositorio de GitHub completo y proporciona recomendaciones de optimización para proyectos Next.js y React

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "analizar_repositorio"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	Yes	Nombre del repositorio
`owner`	Yes	Propietario del repositorio de GitHub
`branch`	No	Rama a analizar (por defecto: main)	main

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls short. It does not disclose whether the operation is read-only, whether GitHub authentication or a token is required, rate/scope limits, whether it clones or indexes the repo, or roughly how expensive/long the analysis is.

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?

A single front-loaded sentence covering action, scope, and value with no filler. It is appropriately sized, though it omits any conditional context that would make it a model of tight structure.

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?

No output schema exists, so the description must cover more than it does. It names the deliverable (optimization recommendations) but leaves unstated the analysis's mechanics, prerequisites, and limitations for a fairly complex repository-wide operation.

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 100%: owner, repo, and branch (with default main) are all documented in the schema. The description adds no extra meaning beyond that, so the baseline of 3 applies.

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?

States a clear verb (analiza) and resource (repositorio de GitHub completo) plus the deliverable (recomendaciones de optimización). The word 'completo' implicitly scopes it apart from the single-file sibling analizar_archivo, though no sibling is named explicitly.

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: the whole-repository scope suggests it belongs after or instead of the file-level siblings, but there is no explicit when-to-use, when-not-to-use, or alternative routing. An agent must infer the placement in the workflow.

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

Deploy Server