Skip to main content
Glama

data-api-code

ndjson_stream_analyze

Validate and profile newline-delimited JSON (.ndjson / .jsonl) logs, detect malformed lines, and summarize schema keys.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ndjson_stream_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description bears the full disclosure burden; it does communicate the operation's outputs (malformed lines, key summary), which implies a read-only analysis. However, it omits size limits, how large files are handled, error behavior, and whether the operation is purely non-destructive, leaving real gaps for an unannotated tool.

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?

A single sentence that front-loads the action verb and packs the format, deliverables, and edge-case handling without filler. It is efficient, if a bit dense as a run-on list.

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?

For a tool with two mutually substitutable input channels, zero schema coverage, no annotations, and no output schema, the description should clarify input selection and return shape. It describes the analysis outputs by name but leaves the input contract and response structure unaddressed.

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?

Schema description coverage is 0% and the description mentions neither parameter. Critically, both text and filePath are optional (required: 0), and the description gives no guidance on precedence when both are supplied or which one is expected.

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 gives specific verbs (validate, profile) tied to a precise resource (newline-delimited JSON .ndjson/.jsonl logs) and names concrete outputs: malformed-line detection and schema-key summarization. The format restriction implicitly separates it from generic JSON validation siblings like json_schema_validate_and_mock, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and nothing tells the agent whether to prefer this over json_schema_validate_and_mock or csv_profile_and_query. It also never says when to supply inline text versus a file path.

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.

Resources