Skip to main content
Glama

Validate Architecture

validate_architecture

Scan your codebase to validate imports and technologies against project architectural guidelines and forbidden tools, catching violations early.

Instructions

Scan the codebase and validate imports/technologies against the project's architectural guidelines and forbidden tools.

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

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.8/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 discloses little: 'scan' and 'validate' imply read-only, but that is never stated, nor is whether the architectural guidelines must already be configured, where they live, or what happens when none exist. The presence of an output schema covers return shape, but prerequisites and side-effect profile remain undocumented.

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?

One front-loaded sentence with no filler, and the action precedes the standard being checked. It is efficient, though the brevity is part of why coverage gaps remain elsewhere.

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?

The output schema removes any need to describe return values, which helps. But for a validation tool in a large sibling set, the definition never says where the architectural guidelines come from or how results should be acted on, leaving the agent under-informed about prerequisites.

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?

The single parameter 'path' has 0% schema description coverage and is never mentioned in the description; 'scan the codebase' only vaguely implies a root directory. Nothing explains that path defaults to '.', whether it scopes the scan recursively, or whether it can target a subdirectory.

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 compound action (scan the codebase, validate imports/technologies) against a named standard (architectural guidelines and forbidden tools). This is clearly distinct from generic verification siblings like verify_work or doctor, though it never names which sibling to prefer.

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 when-to-use guidance, no trigger conditions, and no reference to alternatives such as verify_work, doctor, or assess_project_readiness, which overlap in the 'check the project' space. The agent must infer the occasion for calling this.

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