Skip to main content
Glama

Estimate join output size

bpj_relation_join_size
Read-onlyIdempotent

Estimate inner, left outer and full outer sizes from key frequencies without materializing the join.

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

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes
leftKeyYes
rightKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuinely new behavioral fact: the join is not materialized, so no cost or side effects from building the result set. It says nothing about accuracy, approximations, or which join types it cannot handle.

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 tightly written sentence with the scope (three join types) front-loaded and zero filler. It is efficient, though the compression is part of why the input format is left ambiguous.

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 no output schema and no parameter descriptions, the description does too little: it never states what the result contains (three size estimates?), how the record JSON should be shaped, or how large inputs are handled. Neither the schema nor the annotations fill these gaps.

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 all four parameters are required, with only bare titles. The phrase "from key frequencies" conflicts in spirit with the schema, which asks for "Left records (JSON)" and "Right records (JSON)" — the agent cannot tell whether to supply raw rows, frequency maps, or a sample. leftKey/rightKey are implied by "key" but never connected to the fields, and the 12000-character limits go unmentioned.

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 a specific verb ("Estimate") and a specific resource (inner, left outer, full outer join output sizes), which separates it from siblings like bpj_relation_inner_join that actually execute joins. It stops short of naming those siblings explicitly, so the distinction is inferable rather than stated.

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?

The clause "without materializing the join" implies the intended context — cheap pre-flight estimation before running a real join — but there is no explicit when-to-use/when-not and no named alternative among the many bpj_relation_* siblings. Usage is left 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.