Skip to main content
Glama

Check JSON Lines

bpj_check_json_lines
Read-onlyIdempotent

Validate JSON Lines and report invalid line numbers and valid record types. Blank lines are ignored.

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": {
      "jsonl": "<jsonl>"
    },
    "name": "bpj_check_json_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuine value by disclosing the return content (invalid line numbers and valid record types) and the blank-line handling rule, which matters with no output schema. It says nothing about validation strictness or the 12,000-character input cap.

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?

Two short sentences with zero waste; the core action is front-loaded and the blank-line edge case is a compact trailing clarification.

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 single-parameter read-only validator with no output schema, the description covers purpose, return content, and one edge case. The phrase 'valid record types' is slightly ambiguous and the input size limit is left to the schema, but nothing critical for correct invocation is missing.

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?

There is a single required parameter with 0% schema description coverage; the schema only supplies a title and maxLength. The description implies the input is JSON Lines text but adds no format guidance (e.g., one object per line, no trailing commas, size limit), so it does not fully compensate for the coverage gap.

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?

States a specific verb ('Validate') and resource ('JSON Lines'), plus the reported results (invalid line numbers, valid record types). It is distinguishable from siblings like bpj_format_json or bpj_profile_json_records, though it doesn't name any alternative explicitly.

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?

Usage is only implied: you use it when you have JSON Lines to check. There is no statement of when to prefer this over bpj_profile_json_records (structural inspection) or bpj_format_json, and no prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.