Skip to main content
Glama
Sign In
@forgespace/ui-mcp

@forgespace/ui-mcp

Official
by Forge-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

validate_component_library_setup

Validates a selected component library (shadcn, radix, etc.) is correctly installed and configured in a project directory, detecting setup issues.

Instructions

Validate that a component library is correctly configured in a project directory.

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": {
      "projectPath": "<projectPath>",
      "library": "<library>"
    },
    "name": "validate_component_library_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesAbsolute path to the project directory
libraryYesComponent library to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.25.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full behavioral disclosure burden. It only states the general purpose but does not describe what happens on success/failure, side effects, or return format. This is insufficient for a validation tool.

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?

The description is a single sentence with no extraneous words. However, it lacks behavioral details, but the score for conciseness alone is high.

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

Completeness2/5

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

The tool performs validation but the description does not explain what 'correctly configured' means, what checks are performed, or how results are returned. Given no output schema, this is insufficient for complete understanding.

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%, so the schema already documents both parameters adequately. The description adds no additional parameter meaning beyond what is in the schema, earning a baseline score of 3.

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 clearly states the verb 'Validate' and the resource 'component library is correctly configured in a project directory.' It distinguishes from siblings like 'analyze_component_library' and 'setup_component_library', though not explicitly, so it's a 4.

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 guidance on when to use this tool vs alternatives. There is no mention of prerequisites, context, or exclusions, leaving the agent without decision-making support.

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