Skip to main content
Glama

lint_schema_tool

Validate note frontmatter against enum schemas in _AI_INSTRUCTIONS.md, returning only fields with values outside the declared allowed enums.

Instructions

Validate every note's frontmatter against the enum fields declared in the vault's _AI_INSTRUCTIONS.md (under a "Frontmatter Schema" heading, e.g. status: inbox | active | done | archived). Returns {schema, violations: [{path, field, found, expected_enum}]} — only the deviations, not a full vault dump. A field that's simply missing on a note isn't a violation, only a present value outside the declared enum is. Returns an empty schema/violations pair if no enum schema can be parsed from _AI_INSTRUCTIONS.md.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It thoroughly explains edge cases: missing fields are not violations, only invalid values are; returns only deviations; and returns an empty pair when no schema is parsed. This gives the agent a clear picture of what to expect, though it does not explicitly state that the tool is read-only or describe any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence adds value: it defines the scope, the return format, what counts as a violation, and the edge case of no schema. The purpose is front-loaded, and the structure is clear and efficient without redundancy.

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?

The description is comprehensive for a validation tool: it explains the exact output shape, the rule for violations, and the empty-schema case. It omits only the meaning of the 'vault' parameter, which is a minor gap given the tool's simplicity and optional parameter.

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

Parameters1/5

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

The single parameter 'vault' is completely undocumented. The description never mentions what it represents (path, name, etc.), and schema coverage is 0%. Since the description is the only source of meaning for parameters and it provides none, this is a significant gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool validates note frontmatter against enum fields defined in _AI_INSTRUCTIONS.md. It specifies the action (validate), the resource (every note's frontmatter), and the source of truth (the schema heading). It also distinguishes itself from siblings by focusing on validation rather than reading, writing, or patching notes.

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?

The description makes the tool's purpose obvious, but it does not explicitly state when to use it versus alternatives, nor does it mention any exclusions or alternatives. The usage is implied (e.g., when you need to check enum compliance), but no direct guidance is provided.

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