Skip to main content
Glama

Control character inspection

bpj_dq_control_characters
Read-onlyIdempotent

Locate text containing C0, DEL or C1 control characters.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the detection scope (C0, DEL, C1), which is meaningful beyond the annotations. However, it never says what 'locate' produces - hit counts, offending rows, matched positions, or sample values - and with no output schema that is a real behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and the precise character classes, with no filler or redundant restatement of the tool name. Nothing could be removed without losing meaning.

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?

Two required parameters with no schema documentation, no output schema, and no explanation of the input shape mean the definition is under-specified relative to the tool's complexity. The character-class scope is covered, but an agent cannot confidently construct a call or anticipate the result from this description alone.

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 says nothing about either parameter. The 'rows' parameter is a JSON record-array string capped at 12000 characters and the 'column' parameter names a field to scan, but the description does not convey that the input is a serialized record array, what the length cap means, or how column interacts with rows. For a 0%-coverage, fully required parameter set, the description leaves the caller to guess.

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?

A specific verb ("Locate") plus a specific resource ("text containing C0, DEL or C1 control characters") tells the agent exactly what class of defect is detected. It does not explicitly distinguish itself from near-neighbors such as bpj_find_invisible_characters or bpj_dq_padding_whitespace, so an agent must infer the boundary from the character-class wording alone.

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 guidance on when to choose this over the sibling character-inspection tools, no prerequisites, and no statement of when it should not be used. The agent is left to infer applicability purely from the character ranges named in the single sentence.

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.