Skip to main content
Glama

Ascending order breakpoints

bpj_dq_ascending_order
Read-onlyIdempotent

Locate decreases in a numeric column expected to be nondecreasing.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that the description discloses nothing: it does not say how decreases are reported (row indices? values? count?), whether equal adjacent values count as violations under a "nondecreasing" expectation, or whether the first row is treated specially. With no output schema this leaves the agent guessing at the result shape.

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 clause with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than tight editing.

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 two-parameter check with 0% schema coverage and no output schema, the description should carry the burden of explaining input encoding and result format. It explains neither, so an agent can guess the intent but not reliably construct or interpret a call.

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?

Schema description coverage is 0% — the only documentation is titles ("Record array (JSON)", "Column name"). The description implicitly constrains the column to numeric, which adds a little meaning, but says nothing about the JSON encoding, ordering requirements, the 12000-character limit, or how the column name maps into the supplied rows.

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?

"Locate decreases in a numeric column expected to be nondecreasing" names a specific verb (locate) and a specific defect class (non-monotonic values), which distinguishes it from neighbors like bpj_dq_numeric_range (out-of-range values) or bpj_dq_numeric_type. It is clear what the tool looks for, though it does not explicitly name the checks it is not.

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?

The description gives no when-to-use guidance, no prerequisites (e.g., column must be numeric and sorted by some key), and no pointer to alternatives among the many bpj_dq_* checks. An agent must infer the usage context entirely from the name and one clause.

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.