Skip to main content
Glama

Cell padding whitespace check

bpj_dq_padding_whitespace
Read-onlyIdempotent

Flag text cells with leading or trailing whitespace and pass other scalar types.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

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 establish readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real value by stating that non-text scalar types are passed rather than flagged, which prevents false alarms. However, it never says what a 'flag' looks like in the response (per-cell list? count? row indices?) and there is no output schema to fall back on.

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 zero wasted words; the detection behavior comes first and the type-handling caveat follows. It is efficient, though its brevity leans into under-specification rather than trimming redundancy.

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 tool with 0% schema coverage, no output schema, and two required parameters including a JSON blob, one sentence is not enough. An agent cannot tell how to encode 'rows', what the 'column' selector applies to, or what the returned flags contain, so it may misuse or misread the tool.

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 carries the full burden for the two required parameters and adds nothing about them. It does not explain that 'rows' must be a JSON-encoded record array (max 12000 chars) nor how the 'column' argument selects the cell set to inspect. Only the bare schema titles hint at this.

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 and resource: 'Flag text cells with leading or trailing whitespace.' The added clause 'pass other scalar types' clarifies scope boundaries. It does not explicitly differentiate itself from the nearby normalize_whitespace or visible_whitespace_preview siblings, 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 Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as a normalization tool that would fix rather than flag the whitespace. The only implicit signal is that this is a detection check, which the agent must infer from the verb 'flag'.

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.