Skip to main content
Glama

Left semi join

bpj_relation_semi_join
Read-onlyIdempotent

Retain left records whose keys occur on the right without multiplying rows.

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

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes
leftKeyYes
rightKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful cardinality context with 'without multiplying rows,' but it does not clarify duplicate handling, ordering, key matching rules, or output format beyond that single phrase.

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 definition is a single front-loaded sentence with no filler. Every phrase contributes to defining the semi-join result and row-multiplication behavior.

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 four-parameter data transformation with no output schema and zero schema description coverage, the description is too sparse. It omits input JSON expectations, output shape, duplicate semantics, and key matching details that an agent would need to call this correctly.

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%, so the description must compensate for four required parameters. It only vaguely references left records, right records, and keys; it does not explain the expected JSON string format, whether arrays of objects are required, key column naming, type matching, or duplicate-key behavior.

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 states a specific relational operation: retain left records whose keys occur on the right without multiplying rows. This is clear semi-join semantics and distinguishes the operation conceptually from a full left join, though it does not name any sibling tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the semantics: an agent can infer this is for filtering left records by existence in the right set. There is no explicit guidance on when to prefer this over anti_join, inner_join, left_join, or key_overlap, nor any stated exclusions.

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.