Skip to main content
Glama

Leading-zero code detection

bpj_dq_leading_zero_codes
Read-onlyIdempotent

Locate digit-only text with leading zeros before spreadsheet import.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds that this is a detection scan over a single column, but leaves ambiguous what "locate" yields (matching rows, indices, counts) and whether the input is mutated or merely inspected.

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 of ten words with no filler or repetition. It is efficiently worded, though its brevity is part of why other dimensions are thin.

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?

With no output schema and 0% schema coverage, the definition should explain what the scan returns and how rows/column are supplied. Neither is present, leaving an agent unable to predict the response or correctly format the two required inputs.

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% for both parameters; the only hints are schema titles ("Record array (JSON)" and "Column name"). The description says nothing about the expected JSON shape of rows, whether a header is included, or how column is matched, so it fails to compensate for the coverage gap.

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 resource ("digit-only text with leading zeros"), which separates it from data-quality siblings like whole-number or numeric-type checks. It does not name a sibling alternative, so it stops short of a 5.

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

Usage Guidelines3/5

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

"before spreadsheet import" implies the timing/context in which to call it, which is genuine guidance. There is no explicit when-not, no prerequisite on input shape, and no pointer to the overlapping siblings (whole numbers, numeric type, identifier shape).

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.