Skip to main content
Glama

Expected column inventory

bpj_dq_column_contract
Read-onlyIdempotent

Compare observed fields against a requested schema and list missing and unexpected columns.

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>",
      "expected": "<expected>"
    },
    "name": "bpj_dq_column_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
expectedYes

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully adds that the result surfaces both missing and unexpected columns (valuable since there is no output schema), but says nothing about comparison semantics: case sensitivity, whitespace handling, ordering of results, or what happens with duplicate/extra rows.

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 filler or redundancy; the action and the output content come first. It is efficient, though its brevity is part of the reason the parameter and behavioral gaps remain.

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 descriptions and no output schema means the description is the only source for input formats and return shape, and it provides neither. For a closed-world, idempotent comparison tool the safety side is fine but the callable contract is under-specified.

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% — the two required parameters carry only titles ('Record array (JSON)', 'Expected column names'). The description does not state that 'rows' must be a JSON-encoded array string, nor the format of 'expected' (comma-separated list, JSON array, or object keys), nor how the two relate. With two required params and zero schema coverage, the description should compensate and does not.

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 concrete verb pair ('compare ... and list') and a concrete resource ('observed fields' vs 'requested schema', missing and unexpected columns). An agent knows exactly what the tool returns conceptually. It stops short of 5 because it does not distinguish itself from the near-sibling bpj_check_object_field_contract or the dq_* family.

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 statement, no prerequisites, and no mention of alternatives such as bpj_check_object_field_contract or bpj_dq_allowed_values. Usage is only inferable from the one-line purpose, leaving the agent to guess why this contract check is preferred over the sibling contract check.

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.