Skip to main content
Glama
Sign In
Project Customization MCP

Project Customization MCP

by e1imba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_project

Inspect a VS Code project to detect its type, frameworks, languages, and customization opportunities, helping generate AI-ready configuration files.

Instructions

Analyze a VS Code project structure and detect project type, frameworks, languages, and customization opportunities

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
projectPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3/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 behavioral burden. It implies a read-only analysis and discloses the categories of information produced, but says nothing about permissions, cost, side effects, or whether it writes any artifacts. The output-category list is useful but safety/behavior profile is only implied.

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 efficient sentence that front-loads the verb and resource and packs the detection targets compactly. No filler, though it could add a clause of routing or parameter guidance without bloat.

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 and no annotations, so the description must cover behavior and results. It lists detected categories (a proxy for return values) but omits parameter/default-path semantics and any positioning among the three sibling tools.

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?

One parameter (projectPath) with 0% schema description coverage, and the description never explains it. Notably the parameter is not required, so default-path behavior should be documented but is not, leaving the meaning of omitting projectPath ambiguous.

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 ('Analyze') and resource ('VS Code project structure') and enumerates what it detects: project type, frameworks, languages, customization opportunities. It does not name or contrast with siblings like get_customization_recommendations, so it stops short of full sibling differentiation.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The relationship to siblings (e.g., whether to call this before generate_copilot_instructions or get_customization_recommendations) is left entirely to inference.

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