Skip to main content
Glama

Family Validate

family_validate
Read-only

Validates CSV or JSON variant-family design tables, checking recipes, modes, size keys, duplicates, and per-row values, then reports each problem by row and column.

Instructions

Validate a variant-family design table (issue #138, B1) — a row x column table where row = a variant (keyed by a size designator) and column = a recipe parameter / feature-flag / material. Loads CSV or JSON and checks the recipe, mode, key column, duplicate/missing size keys, and every per-row recipe-door value; each problem names the row+column. Returns {ok, problems}.

table: path to the family table (.csv or .json).

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": {
      "table": "<table>"
    },
    "name": "family_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYes
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.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, closed-world operation. The description adds useful behavior beyond that: it loads CSV or JSON, checks recipe/mode/key-column/duplicate-size/per-row values, names the row and column for each problem, and returns {ok, problems}.

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 front-loaded with the validation purpose and then gives the essential table semantics. The issue reference is not necessary for tool selection, but the rest of the text is dense and mostly earns its place.

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

Completeness4/5

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

For a two-parameter validation tool with annotations and no output schema, the description is largely complete: it explains the input table, what is checked, and the return shape at a high level. It could be stronger by briefly describing the structure of each problem object or mentioning the workspace parameter.

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 coverage is 50%, with workspace already described in the schema and table left undocumented there. The description compensates for the required table parameter by saying it is a path to a .csv or .json family table, but it does not mention the workspace parameter or add further path semantics.

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 states a specific verb and resource: validate a variant-family design table, and explains that rows are variants keyed by size designator and columns are recipe parameters/features/materials. It clearly distinguishes this validation task from general recipe or feature validation, though it does not explicitly name sibling alternatives.

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 implied by the purpose: an agent should call this when it has a family design table to check. However, the description does not state when to use this versus related tools such as recipe_validate, family_materialize, or items_validate, nor does it mention prerequisites or exclusions.

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