Skip to main content
Glama

Project Validate

project_validate
Read-only

Validates a project.json container by checking schema, naming, paths, referenced manifest and item registry, components directory, and master/skeleton component existence.

Instructions

Validate a project.json container (issue #143 / D1): the schema stamp ("ankusdrive.project/1"), the naming convention on the project name, the conventional path fields, and — relative to the project directory — that the referenced manifest + item registry exist, the components directory is present, and a named master/skeleton is a real component of the assembly manifest.

project: path to the project.json container.

Returns {ok, problems, schema, name} — ok is True iff problems is empty.

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": {
      "project": "<project>"
    },
    "name": "project_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the exact meaning of a pass (`ok` is True iff `problems` is empty) and that path checks are evaluated relative to the project directory — details an agent cannot read off the annotations.

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 check list is front-loaded and each enumerated item is load-bearing because it defines the contract of the tool. Minor waste in the internal ticket reference '(issue #143 / D1)' and in splitting the return-value sentence below the parameter note, but the definition is still tight for what it covers.

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?

For a two-parameter read-only validator with no output schema, the description supplies the full picture: what is verified, how relative paths are resolved, and the shape and semantics of the return value. An agent can decide to call it and interpret the result without further information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: `workspace` is documented in the schema but `project` is bare. The description compensates by defining `project` as the path to the project.json container, which is the essential meaning an agent needs; it adds nothing for `workspace`, but that gap is already covered by the schema.

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 (validate) and a precisely bounded resource (a project.json container), then enumerates the exact invariants checked: schema stamp, name convention, path fields, manifest/item-registry existence, components dir, and master/skeleton membership. This scope is distinctive against siblings like validate_manifest, items_validate, and project_check_references, though none of those siblings is named to make the boundary explicit.

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: you call it on a project.json to check integrity. There is no statement of when to prefer it over validate_manifest, items_validate, project_check_references, or project_resolve_manifest, and no prerequisites (e.g. that a project workspace must already be open) are given.

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