Skip to main content
Glama

Inclusive numeric range validation

bpj_dq_numeric_range
Read-onlyIdempotent

Flag nonnumeric cells and numbers outside the inclusive user-defined interval.

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>",
      "minimum": "<minimum>",
      "maximum": "<maximum>"
    },
    "name": "bpj_dq_numeric_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes
maximumYes
minimumYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the interval is inclusive and nonnumeric cells are reported alongside out-of-range numbers. It does not say what a 'flag' looks like in the response, whether rows are dropped or merely reported, or what happens when minimum exceeds maximum.

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 tight sentence with no filler, and the core condition (inclusive interval) is front-loaded. It could be slightly better structured by separating what is flagged from how bounds are interpreted, but nothing is wasted.

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?

Four required parameters at 0% schema coverage, no output schema, and no explanation of the expected 'rows' encoding or the result format leave real gaps for an agent trying to invoke it. For a validation tool whose whole value is the diagnostic output, the definition should at least state what is returned and how nonnumeric cells are treated.

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 the parameter burden. It does supply the key semantic point that bounds are inclusive, which the schema's bare 'minimum'/'maximum' titles do not convey. However, the 'rows' parameter — a JSON-encoded record array string with a 12000-character cap — is never mentioned, and 'column' is only obliquely implied by 'cells'.

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 ('flag') and a precise resource: nonnumeric cells and numbers outside a user-defined inclusive interval. It is clear what the tool checks, but it never distinguishes itself from the closely related bpj_dq_numeric_type sibling, which appears to overlap on the nonnumeric-cell flagging.

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 or when-not-to-use guidance and no named alternative, despite an obvious overlap with bpj_dq_numeric_type. The only implied usage is validating one column's numeric values against a min/max window, which the agent must infer from the wording.

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.