Skip to main content
Glama

Required cell check

bpj_dq_required_cells
Read-onlyIdempotent

Locate absent, null or whitespace-only cells in a required column.

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": {
      "rows": "<rows>",
      "column": "<column>"
    },
    "name": "bpj_dq_required_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description's contribution is defining what counts as a defect — absent, null, or whitespace-only — which is genuinely useful semantic context. It says nothing about what is returned (row indices, counts, offending values) or how large inputs are handled, so it adds moderate but not rich context beyond the annotations.

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 front-loaded sentence with no filler, and the defining qualifier (what counts as a missing cell) appears immediately. It is efficient, though its brevity contributes to the gaps in parameter and output explanation rather than merely reflecting a simple tool.

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?

For a two-parameter tool with clear annotations and no output schema, the description covers the core semantics adequately. However, the opaque 'rows' JSON-string parameter and the unspecified return shape mean an agent still lacks information needed to call it confidently, so completeness is only partial.

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%, so the description carries the full burden, and it largely does not. It hints at the 'column' parameter via 'required column' but never explains that 'rows' is a JSON-encoded record array (only the schema's title reveals this) or how the column name is matched. Neither parameter's format, casing expectations, or the 12000/160 maxLength constraints are addressed.

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 ('Locate') and a precisely defined resource: cells that are absent, null, or whitespace-only in a required column. The enumerated failure modes ('absent, null or whitespace-only') distinguish it from neighboring checks such as padding/whitespace or sparse-row tools. It stops short of naming a sibling to route away from, so a 4 rather than 5.

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 explicit when-to-use guidance, no prerequisites, and no stated alternative. With many overlapping data-quality siblings (bpj_dq_sparse_rows, bpj_dq_padding_whitespace, bpj_dq_column_contract), the agent must infer which check applies from the name and one-line description alone. Usage is only implied, not directed.

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.