Skip to main content
Glama

Full outer join

bpj_relation_full_join
Read-onlyIdempotent

Include matched pairs and unmatched records from both input tables.

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

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes
leftKeyYes
rightKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds nothing beyond result content. It says nothing about how unmatched rows are represented (null padding), what happens with duplicate or many-to-many keys, or what the returned structure looks like despite there being no output schema.

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 and no repetition of the title. It is efficient, but the brevity reflects under-specification rather than disciplined compression.

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-required-parameter tool with zero schema coverage and no output schema, this definition is too thin. An agent still needs to know the input JSON format, key-matching behavior, and output shape in order to invoke it correctly, and none of that is present.

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 carries the burden, yet it mentions no parameters at all. The schema titles hint that left/right are JSON record strings and leftKey/rightKey are column names, but the 12000-char limits, required-ness of all four, and expected JSON shape are never reinforced or explained.

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 sentence names the join semantics precisely: matched pairs plus unmatched rows from both sides. That implicitly separates it from bpj_relation_inner_join (matched only) and bpj_relation_left_join (unmatched from one side), though it never names the siblings or the operation directly.

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 of a full outer join; there is no explicit when-to-use statement, no conditions favoring this over left/inner/anti joins, and no prerequisites such as key compatibility between leftKey and rightKey.

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.