lava-mcp

by mattface

Overview Schema Source Related Servers Discussions Admin

Hybrid

validate_job

Check a YAML job definition for errors without submitting it.

Instructions

Validate a YAML job definition without submitting it.

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": {
      "definition": "<definition>"
    },
    "name": "validate_job"
  }
}

Input Schema

Name	Required	Description	Default
`definition`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 19, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It does not explain what validation checks are performed, what happens on success or failure, or any side effects, leaving the agent with minimal behavioral context.

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?

The description is a single concise sentence that conveys the core purpose without any unnecessary words, earning its place.

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?

Given the tool's simplicity (1 param, no output schema, no annotations), the description omits critical information such as the return format (e.g., boolean, list of errors), usage constraints, and how it complements related siblings like get_job_definition.

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?

With 0% schema description coverage, the description adds minimal value by specifying the parameter is a 'YAML job definition', but it lacks details on format, constraints, or examples, which are needed for proper parameter understanding.

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 verb 'Validate' and the resource 'a YAML job definition', and adds the qualifier 'without submitting it', which distinguishes it from sibling tool submit_job.

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 phrase 'without submitting it' implies a dry-run use case, but there is no explicit guidance on when to use validate_job over alternatives like submit_job or how it relates to other validation-related tools.

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