Skip to main content
Glama

Blend Join Types

blend_join_types
Read-only

Read current blend merge types and Union feature availability from the connected report browser without saving or changing the report.

Instructions

Read current native blend merge types and Union feature availability.

Resolves the selector enum from the connected browser, without saving or changing the report. Union uses its own saved tree node, unlike ordinary joins. Availability does not imply this MCP can yet write all join types or that any particular input/key configuration is valid.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blend_join_types"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real context beyond that: it will not save or mutate the report, Union uses its own saved tree node, and reported availability does not mean the MCP can write every join type or that a given input/key configuration is valid. That caveat set is genuinely useful behavioral disclosure, short only of any note on error or connection-failure behavior.

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?

Front-loaded with the core action in the first sentence, followed by the caveats. Slightly verbose line wrapping and the trailing validity disclaimer, but each clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value detail is unnecessary. The description covers scope, mutation safety, and capability limits; the main remaining gap is the meaning and default behavior of the optional report_id, which matters for calling it 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?

The single parameter report_id is nullable with default null and 0% schema description coverage, and the description never mentions it — it does not say whether omitting it falls back to the currently connected report or what happens with an unknown id. With one undocumented parameter the description should compensate and does not.

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?

States a specific verb and resource: 'Read current native blend merge types and Union feature availability.' An agent knows it is an introspection/read tool about join types, though it doesn't explicitly distinguish itself from siblings like blends_joins or blend_get.

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 implied rather than stated: the note that it does not save or change the report and that it 'resolves the selector enum from the connected browser' suggests it is a pre-flight/inspection call, but there is no explicit when-to-use or when-not-to-use guidance relative to alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools