Skip to main content
Glama

Unicode NFC consistency

bpj_dq_unicode_nfc
Read-onlyIdempotent

Find text cells whose code-point sequence changes under NFC normalization.

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

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 this a read-only, idempotent, non-destructive, closed-world check, so the safety profile needs no restating. The description contributes the actual matching semantics (code points change under NFC), which is real behavioral substance. It does not disclose the result shape, whether all offending cells or only the first per column are reported, or any cap on output.

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?

A single front-loaded sentence with no filler, hedging, or repetition. Nothing could be trimmed without losing the detection criterion.

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 whose inputs are an undocumented JSON-string record array and a bare column name, with no output schema and no annotation help on parameters, the definition is too thin. An agent cannot tell from the description how to format 'rows', what a match result looks like, or what happens when the column is absent or non-text.

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 two required parameters, so the description carries the full burden and provides almost nothing. 'Text cells' loosely implies the column must hold strings, but the critical detail that 'rows' is a JSON-encoded record array string (max 12000 chars) versus the column name string is left entirely unexplained.

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 gives a specific verb plus a precise detection criterion: find text cells whose code-point sequence changes under NFC normalization. That is far more informative than the bare name and distinguishes it from neighboring data-quality checks such as padding/whitespace or control-character checks. It stops short of naming which sibling to use instead when the concern is a different Unicode property (script, category, escape sequences).

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 explicit when-to-use or when-not-to-use guidance, no mention of alternatives among the unicode_* or dq_* siblings, and no note on how to act on a hit. The use case (verifying text is in canonical composed form before comparison or joining) must be inferred entirely from the criterion.

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.