Skip to main content
Glama

Allowed-value membership check

bpj_dq_allowed_values
Read-onlyIdempotent

Check typed scalar membership against an explicit JSON allowlist.

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>",
      "allowed": "<allowed>"
    },
    "name": "bpj_dq_allowed_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes
allowedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds only that comparison is type-aware against an 'explicit' allowlist; it says nothing about how non-matching or null/absent values are handled, whether types are coerced, or what the check returns.

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 redundancy or filler. However, its brevity is bought at the cost of the conventions the agent needs, so it is efficient rather than complete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description could explain what result shape a membership check produces, and the JSON-in-string parameters demand format guidance that is absent. Compared with a simple scalar-parameter tool this is thin, though the annotations and the compact three-parameter surface limit the damage.

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 coverage is 0% and all three parameters are plain strings, including two that actually carry JSON payloads ('rows' record array, 'allowed' scalar list). The description hints at a JSON allowlist but never explains the encoding of 'rows' or the required format of 'allowed', leaving the non-obvious string-encoded JSON structure undocumented.

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 verb+resource pair ('check typed scalar membership against... allowlist') is specific and identifies a data-quality membership check. It is distinguishable from siblings like bpj_dq_numeric_range or bpj_dq_column_contract, though it doesn't name the nearest alternative (e.g. numeric range) explicitly.

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 prerequisite such as what 'typed scalar' means in practice, and no mention of when a different DQ sibling should be used instead. The agent must infer the applicable scenario from the name alone.

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.