Skip to main content
Glama

Coalesce alternative fields

bpj_table_coalesce
Read-onlyIdempotent

Select the first nonblank cell across ordered fallback columns into a new field.

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": {
      "rows": "<rows>",
      "columns": "<columns>",
      "target": "<target>"
    },
    "name": "bpj_table_coalesce"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
targetYes
columnsYes

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 the safety profile is covered. The description adds that a new field is created and that column order determines precedence, but it does not say what happens when every fallback column is blank, whether values are type-coerced, or how errors are reported.

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 front-loaded sentence with no filler; the operation, the precedence rule and the output location are all packed in without redundancy.

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

Completeness3/5

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

With three required parameters, no output schema and zero schema description coverage, the definition is minimally adequate. It conveys the core transformation but omits the input encoding format, all-blank behavior and result shape, which matter for correct invocation.

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 must carry parameter meaning. It contributes one genuinely useful signal — the columns list is ordered by fallback priority — but says nothing about the rows parameter's JSON record-array encoding, the target column's constraints, or the string-length limits, all of which the agent must guess from titles alone.

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 gives a specific verb and outcome: take the first nonblank cell across ordered fallback columns and write it into a new field. That is distinguishable from fill-style siblings, but it does not name or contrast any alternative tool, so it stops short of a 5.

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 explicit when-to-use or when-not-to-use guidance, and no reference to adjacent tools such as the forward/backward fill or combine-fields operations. Usage is only implied by the one-line mechanics, leaving the agent to infer the selection context.

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.