Skip to main content
Glama

Left outer join

bpj_relation_left_join
Read-onlyIdempotent

Keep every left record, inserting a null right record for unmatched keys.

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

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes
leftKeyYes
rightKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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 genuine behavioral value by explaining the null-padding of unmatched right rows, but says nothing about input format expectations, size limits (12000 chars), or how malformed JSON is handled.

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?

A single sentence with the defining constraint front-loaded and no filler. Every word earns its place; the problem is omission elsewhere, not verbosity here.

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?

With four required parameters, zero schema description coverage and no output schema, a one-line description leaves too much unspecified — the JSON row format, key-column semantics, and the shape of the resulting joined records are all undocumented. It explains the join semantics well but not how to actually call the tool.

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% and the schema offers only bare titles ('Left records (JSON)', 'Left key column'), so the description carries the burden. It gestures at records and keys implicitly but never explains that left/right are JSON-encoded row collections, what shape those rows take, or that keys must be column names present in both sides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence defines the operation by its exact semantics — 'Keep every left record, inserting a null right record for unmatched keys' — which is precisely what separates a left outer join from the inner, full, semi and anti join siblings. An agent can classify the tool without opening the schema.

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 mention of when a different join type is preferable, and no prerequisites. The reader must already know SQL join taxonomy to know when to reach for this tool rather than bpj_relation_inner_join or bpj_relation_full_join.

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.