Skip to main content
Glama

Functional dependency conflicts

bpj_dq_functional_dependency
Read-onlyIdempotent

Find source keys mapped to multiple distinct values in a dependent column.

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>",
      "group": "<group>",
      "column": "<column>"
    },
    "name": "bpj_dq_functional_dependency"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
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 declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds the detection semantics themselves (a key mapping to multiple distinct values), which is useful behavioral content. It says nothing about how many violations are returned, how the rows payload is parsed, or what the result looks like, so the addition is modest.

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 filler, and the core detection rule comes first. It is efficient, though the terse jargon density makes it slightly harder to parse than a plainer phrasing would be.

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 three-param tool with no schema descriptions, no output schema, and a string-serialized JSON payload, one sentence is thin. The agent does not learn the expected format of 'rows', whether 'group' accepts compound keys, or anything about the returned violation report.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden. It does clarify the roles of the two otherwise indistinguishable string params: 'source keys' maps to 'group' and 'dependent column' maps to 'column'. However, the most complex parameter, 'rows' (a JSON record array as a string, max 12000 chars), gets no explanation of expected structure, and 'group' being plural-key capable is unstated.

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 uses a specific verb ('Find') plus a precise definition of the check: keys mapped to multiple distinct values in a dependent column. That is a genuine functional-dependency violation, so an agent can understand the operation. It loses a point because it never names the concept ('functional dependency violation') nor distinguishes itself from the nearby bpj_dq_duplicate_key sibling, which an agent could easily confuse with a key/value consistency check.

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, no exclusions, and no mention of alternatives. Nothing tells the agent when to pick this over bpj_dq_duplicate_key or bpj_dq_column_contract, and no prerequisites about data shape or expected row structure are given.

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.