SwishrJobs

JSON Lines checker: locate the bad line in an NDJSON stream

submit_json_ndjson_check

Idempotent

Validate a JSON Lines (NDJSON) stream and report the line number and parser error of every line that is not valid JSON, so a broken export can be fixed without bisecting it. Choose this when a JSON Lines or NDJSON file fails to load and you need the exact line number and parser error rather than bisecting the file. Do not choose this for a single multi-line JSON document; use json-schema-validation or json-key-audit. Example requests: Find the broken line in this JSON Lines export. | Which lines of this NDJSON file are invalid? | Validate this jsonl stream before I load 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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_json_ndjson_check"
  }
}

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.

AddedNov 3, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with them. However, the tool is a priced capability requiring quote_id and authorized_by, and readOnlyHint=false signals a side effect (a charged job) that the description never explains; an agent gets no warning about cost or the quote/authorize flow before invoking it.

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 the core purpose, then routing guidance, then examples – a sound structure. There is mild redundancy: 'so a broken export can be fixed without bisecting it' and 'rather than bisecting the file' make the same point twice, and the example list adds bulk beyond what the two sentences already establish.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the input format is covered. The gap is behavioral rather than structural: for a job-submission tool with a quote/price authorization protocol, omitting any mention of pricing or the quote_id requirement leaves the agent underprepared for the actual call sequence.

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%, and the nested fields (content with its 1 MB limit, quote_id, accepted_price) are already well documented in the schema itself. The description adds only the format framing ('JSON Lines / NDJSON stream') and says nothing about the outer 'inputs' wrapper or authorized_by, so it neither compensates for nor extends the schema meaningfully.

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 names a specific verb and resource ('Validate a JSON Lines (NDJSON) stream') plus the exact output it produces ('line number and parser error of every line that is not valid JSON'). It explicitly distinguishes itself from json-schema-validation and json-key-audit, so an agent can route correctly without opening any schema.

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?

It states both the positive trigger ('when a JSON Lines or NDJSON file fails to load and you need the exact line number... rather than bisecting') and the exclusion ('Do not choose this for a single multi-line JSON document'), naming the alternative tools to use instead. The three example requests reinforce the routing decision with realistic phrasings.

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?