Skip to main content
Glama

Key domain coverage

bpj_relation_key_overlap
Read-onlyIdempotent

List shared and side-only nonblank keys and calculate coverage for both key domains.

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": {
      "left": "<left>",
      "right": "<right>",
      "leftKey": "<leftKey>",
      "rightKey": "<rightKey>"
    },
    "name": "bpj_relation_key_overlap"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes
leftKeyYes
rightKeyYes

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?

The annotations already establish that this is a read-only, idempotent, non-destructive operation in a closed world. The description adds useful behavior beyond that by specifying nonblank-key filtering and coverage across both key domains, but it does not disclose matching semantics, case sensitivity, duplicate handling, or the shape of the result.

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?

The description is a single front-loaded sentence with no filler or repetition. Every element contributes to the stated purpose, even though the brevity leaves gaps addressed in other dimensions.

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?

This is a four-parameter tool with no schema parameter descriptions and no output schema, making the description the main source of context. It states the high-level purpose but omits input format expectations, key-matching details, and how coverage is calculated, which is insufficient for reliable invocation.

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% across four required parameters, so the description needs to compensate and does not. It never maps 'left', 'right', 'leftKey', or 'rightKey' to their roles, and only vaguely gestures at 'both key domains' without explaining the expected JSON records or key-column inputs.

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 names specific operations ('List' and 'calculate coverage') and a specific resource ('shared and side-only nonblank keys'). It is clear enough to distinguish this as a key-overlap/coverage tool, though it does not explicitly differentiate itself from sibling relation tools such as foreign-key or cardinality checks.

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 use this tool versus related relation tools, nor any stated prerequisites or exclusions. The description says what it does but leaves the choice between this and neighboring coverage/join/foreign-key tools entirely to inference.

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.