Skip to main content
Glama

Uppercase business identifier check

bpj_dq_identifier_shape
Read-onlyIdempotent

Check codes beginning with a capital letter and composed of uppercase alphanumeric segments separated by single hyphens.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the operation read-only, idempotent, closed-world and non-destructive, so the safety profile is covered and the description's main added value is the acceptance rule itself. It does not disclose what happens on a mismatch (rejected row, flagged record, count of violations), whether matching is case-sensitive or unicode-aware, or any limits on input size, though maxLength on rows hints at a cap.

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, keeping the rule itself immediately visible. The brevity is close to under-specification, but no sentence in the description is wasted.

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, no-output-schema check with a simple contract, the description covers the semantic rule but leaves the input contract and the result shape unexplained. An agent knows what pattern is being validated but not how to package rows/column or how findings are reported.

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% and the description never mentions the two parameters. It does not explain that 'rows' is a JSON-encoded array of records or that 'column' names which field to test, so an agent must rely on the terse schema titles alone. With an uncovered parameter set, the description should have compensated and does not.

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 states a specific verb and resource ('Check codes') and precisely defines the accepted pattern: capital leading letter, uppercase alphanumeric segments, single hyphens. It is clear what class of data quality rule this is, though it never states that the check operates on rows of a column, so the tie to a data-quality scan workflow must be inferred from the sibling names.

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?

Usage is implied by the pattern definition: use it when validating a column expected to hold uppercase hyphen-segmented identifier codes. There is no explicit when-to-use versus when-not-to-use, no mention of sibling checks such as bpj_dq_leading_zero_codes or bpj_dq_allowed_values, and no note that similarly shaped formats would be misclassified by this rule.

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.