Skip to main content
Glama

analyze_project

Inspect React Native, React, Next.js, Flutter, or Angular projects without changes to detect framework, language, package manager, i18n setup, locales, namespaces, structure, and config warnings.

Instructions

Analyze a React Native project (as well as React, Next.js, Flutter, and Angular) without modifying anything. Returns framework, language, package manager, detected i18n library, configuration, locale directory, source and target locales, existing namespaces, project structure, and configuration warnings.

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

Input Schema

NameRequiredDescriptionDefault
projectPathNoOptional path to the project root directory. Defaults to the current working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it explicitly declares the operation is non-mutating ('without modifying anything') and enumerates every category of value returned, including configuration warnings. Gaps remain around failure modes (unsupported frameworks, invalid paths) and whether warnings require action, but the core safety profile is disclosed.

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?

Two sentences, front-loaded with the capability and the non-destructive guarantee, then a dense enumeration. The long return list would normally be bloat, but since there is no output schema it substitutes for one and every item earns its place.

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

Completeness5/5

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

There is no output schema, and the description compensates by listing the return payload comprehensively, plus a clear side-effect guarantee. For a single-optional-parameter read-only tool this covers everything an agent needs to select and invoke it; only interpretation guidance for the reported warnings is missing.

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% and the single parameter is fully documented in-schema ('Optional path to the project root directory. Defaults to the current working directory'). The description adds no syntax, format, or default-behavior detail beyond that, so the baseline 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 specific verb and resource ('Analyze a React Native project ... as well as React, Next.js, Flutter, and Angular') and enumerates exactly what it detects, so the agent knows this is a framework/inspection tool. It does not explicitly contrast itself with i18n siblings like generate_i18n_plan, though 'without modifying anything' implicitly separates it from the mutation tools.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternative. The agent must infer that this is a discovery step preceding generate_i18n_plan or apply_i18n_plan from the sibling list alone, which the description never references.

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