designsafe-mcp

Overview Schema Source Related Servers Discussions Admin

validate_job

Validate job submissions against schema requirements and input existence before spending service units, ensuring only valid jobs run.

Instructions

Schema and sanity checks plus input existence, before any SU is spent.

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

Input Schema

Name	Required	Description	Default
`job`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the tool does not spend SU (implied by 'before any SU is spent') and focuses on validation, but it does not explain error handling, return value structure, or whether it has 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?

The description is a single sentence that immediately states the core function and context. Every word is purposeful, with no redundant information.

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 role in a job submission workflow and lack of annotations, the description is too sparse. It does not explain what specific sanity checks are performed, how to interpret results, or how this step relates to sibling tools like build_job_request or submit_job.

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 schema has zero description coverage, and the description only vaguely references 'input existence' without explaining the structure or requirements of the 'job' object. This provides minimal guidance beyond the raw 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?

The description clearly states the tool performs 'Schema and sanity checks plus input existence,' which is a specific verb+resource combination. It distinguishes this tool as a validation step in the job workflow, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before any SU is spent' provides a clear temporal context for when to use this tool. However, it does not explicitly state when not to use it or mention alternative validation tools, so it falls short of a 5.

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