Skip to main content
Glama

Inner join of two record sets

bpj_relation_inner_join
Read-onlyIdempotent

Return matching left-right record pairs and retain every duplicate-key combination.

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

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes
leftKeyYes
rightKeyYes

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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds one genuinely useful behavioral fact beyond them: duplicate-key combinations are all retained rather than collapsed, which materially affects result size. It says nothing about how keys are compared (string vs numeric), what happens with malformed JSON, or what the returned structure looks like.

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; the multiplicity rule is appended where it matters most. The terseness borders on under-specification rather than padding, but nothing in the sentence is wasted.

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 join tool with no output schema and zero schema descriptions, the definition is too thin: key comparison rules, JSON encoding expectations, and result shape are all unaddressed. The one thing it does clarify — duplicate retention — is the most valuable single fact, but it cannot substitute for the missing parameter and output context.

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% for four required parameters, so the description must carry the load and does not: it never explains that 'left'/'right' are serialized JSON record arrays subject to a 12000-character cap, nor that leftKey/rightKey name the join columns. Only the shared notion of 'key' is gestured at. The schema's titles are mildly self-explanatory, which keeps this from a 1.

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?

'Return matching left-right record pairs' names a specific operation and 'retain every duplicate-key combination' pins down the inner-join semantics, so an agent can tell this apart from the outer-join siblings in broad strokes. It never explicitly contrasts itself with left/full/anti joins by name, leaving full sibling differentiation to the title rather than the description.

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 or when-not-to-use guidance, no mention of when a different join variant (left, full, semi, anti) would be the right choice, and no prerequisites or input-format expectations. The word 'matching' hints at the inner-join condition, but the agent must infer that from the domain rather than being told.

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.