Skip to main content
Glama

Boolean flag type check

bpj_dq_boolean_cells
Read-onlyIdempotent

Find flags stored as text, numbers or null instead of JSON booleans.

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_boolean_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only a restatement of the detection rule and says nothing about what a finding looks like, whether one row is reported or all offenders, or how results are shaped — a gap that matters because there is no output schema.

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 or redundant phrasing. It is efficient, though its brevity borders on under-specification rather than deliberate tightness.

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 that takes a raw JSON record array plus a column name, returns no output schema, and documents no parameters, one sentence is far too thin. An agent knows what defect is sought but not what inputs to construct or what it will receive back.

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 must carry parameter meaning, yet it never mentions 'rows' or 'column'. The word 'flags' hints that the column should hold flag values, but it does not explain that 'rows' is a JSON record array capped at 12,000 characters or that 'column' names the single field to scan.

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 a concrete verb ('Find') and a precise defect definition: values that are text, numbers, or null where JSON booleans belong. That distinguishes it from a generic type check and from siblings like bpj_dq_numeric_type or bpj_dq_mixed_types, though it never names an 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 Guidelines2/5

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

There is no statement of when to run this check, what prerequisite state it assumes (e.g., a column expected to be boolean-typed), or which sibling to use instead when the goal is a different data-quality check. The agent must infer usage from the tool name and the list of siblings.

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.