Skip to main content
Glama

Maximum field length check

bpj_dq_maximum_text_length
Read-onlyIdempotent

Enforce a Unicode code-point limit for text cells and report nontext rows.

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>",
      "limit": "<limit>"
    },
    "name": "bpj_dq_maximum_text_length"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
limitYes
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 establish readOnly/idempotent/non-destructive behavior, so the description only needs to add context. It does add two useful facts: the limit is measured in Unicode code points (not bytes or UTF-16 units) and nontext rows are reported rather than silently ignored. It does not say what the report looks like, whether violations are returned in full or capped, or what 'enforce' produces, which is a gap for a tool with 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 repetition. It is lean to the point of terseness, but the tightness itself is not the problem — the missing detail belongs to completeness, not verbosity.

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 zero parameter description coverage, a one-sentence description is not enough. An agent still cannot tell what the result contains (violation list? truncated values?), what happens to nontext rows in the output, or how to format the rows argument.

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 has to compensate. It clarifies that 'limit' is in code points and that the check applies to a named column, but it never explains that 'rows' is a JSON-encoded record array supplied as a string, nor how 'column' is matched against fields. Half the parameters remain ambiguous despite the description.

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+resource: enforce a Unicode code-point limit on text cells in a column, and additionally report nontext rows. That is concrete enough to distinguish it from siblings like bpj_line_length_distribution or bpj_dq_required_cells, though no sibling is named explicitly.

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 only implied by the operation itself (a data-quality length check); there is no explicit statement of when to pick this over adjacent checks such as bpj_line_length_distribution or bpj_dq_column_contract, and no exclusions or prerequisites.

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.