SwishrJobs

JSON Schema validation of a document

submit_json_schema_validation

Idempotent

Validate a JSON document against a JSON Schema and report every violation with its JSON Pointer path and the keyword that failed. Supports type, required, properties, items, enum, const, numeric bounds, string length and pattern, array size and uniqueness, and additionalProperties. Choose this when you have a concrete JSON document and a JSON Schema and need every violation located by JSON Pointer path and failing keyword. Do not choose this when you need a validator module for your own service (use webhook-payload-validation), or when the schema relies on $ref, allOf, anyOf or oneOf, which this documented subset does not evaluate. Example requests: Validate this JSON payload against my schema and list the failures. | Which fields in this webhook payload violate the schema? | Check this API response against its JSON Schema.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_json_schema_validation"
  }
}

Input Schema

Name	Required	Description
`inputs`	Yes
`quote_id`	No	The quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
`authorized_by`	Yes	Identifier of the human or agent authorizing this job.
`accepted_price`	No	The amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

Name	Required	Description
`quote`	No
`state`	Yes
`job_id`	Yes
`artifacts`	No
`access_token`	No	Per-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
`verification`	No	Independent verification. verification.ok = false means the job failed, not a partial success.
`capability_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare idempotent, non-destructive, closed-world behavior, but the description adds the valuable disclosure of the supported keyword subset and the composition keywords it does not evaluate. It does not mention that this is a paid job requiring quote authorization, though the schema documents that.

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?

Front-loaded with purpose and scope followed by exclusions, then example requests that aid matching. It is somewhat long with the example block, but each part 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 validation tool with a rich input schema and an output schema, the description covers scope, limitations and routing. The only gap is not surfacing the job/quote authorization flow, which the schema carries.

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 description coverage is 75%, so most parameters are already documented in the schema. The description adds no parameter-level meaning (content structure, quote_id, authorized_by, accepted_price), so it sits at the baseline for high-coverage schemas.

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?

States a specific verb and resource (validate a JSON document against a JSON Schema) and specifies the output form: every violation with its JSON Pointer path and failing keyword. This is distinguishable from sibling tools such as submit_json_schema_inference or submit_webhook_payload_validation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states when to choose this ('you have a concrete JSON document and a JSON Schema') and when not to, naming an alternative (webhook-payload-validation) and a hard limitation ($ref, allOf, anyOf, oneOf not evaluated). Nothing is left to inference about selection.

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

All SwishrJobs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?