Skip to main content
Glama

Combine field text

bpj_table_combine_fields
Read-onlyIdempotent

Combine selected fields in order into a new display field with a literal separator.

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>",
      "separator": "<separator>",
      "target": "<target>"
    },
    "name": "bpj_table_combine_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
targetYes
columnsYes
separatorYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds genuinely useful semantics beyond that: concatenation happens 'in order' and the separator is 'literal' (no escaping or interpretation), and the result lands in a new display field rather than replacing inputs. It stops short of saying how empty or non-string cell values are treated.

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 or redundancy; every clause contributes (selection, ordering, separator, output field). It is lean to the point of being slightly thin for a four-required-parameter tool, but nothing 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 tool with four required parameters, no output schema, and no parameter descriptions, the definition does not say enough: the JSON-string encoding of rows and columns, the expected shape of records, handling of missing values, and the returned column type are all absent. Annotations cover only the safety profile, so the description is the sole place these details could live and it omits them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the burden and does map conceptually onto all four parameters: 'selected fields in order' implies the columns list and its ordering, 'literal separator' maps to separator, and 'new display field' maps to target. It does not compensate for the most error-prone aspect, that rows and columns must be passed as JSON-encoded strings rather than arrays, nor does it explain that target must not collide with an existing column.

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 states a specific verb and resource ('Combine selected fields ... into a new display field') and names the resulting artifact plus the role of the separator, so the operation is unambiguous. It does not distinguish itself from nearby siblings such as bpj_table_coalesce (which picks a single value) or bpj_table_explode_delimited (which splits), leaving the agent to infer the boundary.

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 guidance, no prerequisites, and no mention of an alternative tool for related reshaping tasks. The agent is told what the tool does but not the condition under which it should be chosen over the many other bpj_table_* tools.

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.