Skip to main content
Glama

Unpivot measurement columns

bpj_table_unpivot
Read-onlyIdempotent

Expand selected measurement columns into field-value rows with one-based source row numbers.

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>"
    },
    "name": "bpj_table_unpivot"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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, so safety and repeatability are covered. The description contributes one genuinely useful behavioral fact beyond that: output rows carry one-based source row numbers. It does not say what the resulting field/value columns are named, whether column order is preserved, or what happens to non-selected columns.

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 zero filler and no restatement of the title. It is efficient, but the brevity comes at the cost of details that the low schema coverage makes necessary.

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?

For a two-parameter pure transform with annotations covering safety and no output schema, the description covers the core semantics. Given 0% schema description coverage, however, it should at minimum explain the JSON-string encoding of rows and columns and the shape of the produced rows — gaps an agent would hit on first 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 the parameter burden, yet it only implies that 'selected measurement columns' comes from the columns argument. It never explains that both arguments are JSON-encoded strings rather than native arrays, which is the biggest invocation risk here; only the schema titles hint at it.

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 concrete verb+resource: 'Expand selected measurement columns into field-value rows', which pins down an unpivot/melt operation and its result shape. It is clear on its own, but adds no differentiation from similar reshape siblings (e.g., bpj_table_explode_delimited or bpj_table_column_arrays), leaving the agent to infer which reshape tool applies.

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 when NOT to use it or which alternative handles a different reshape case. The agent gets a definition but no routing signal among the ~30 bpj_table_* siblings.

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.