Skip to main content
Glama

Record array to column vectors

bpj_table_column_arrays
Read-onlyIdempotent

Convert a collection of records to aligned column arrays, filling absent cells with null.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact: absent cells are filled with null, which tells the agent ragged records are tolerated. It says nothing about ordering guarantees or handling of malformed input, so it adds moderate value only.

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?

One sentence, front-loaded with the operation and ending with the only non-obvious behavior (null filling). Nothing is wasted, though brevity here edges toward under-specification rather than true crispness.

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?

The tool is simple, annotated, and has no output schema to explain, so the bar is modest. Still, for a 0%-coverage single-parameter tool whose parameter is a JSON string, the definition should state the input encoding and roughly what the output looks like (arrays keyed by field name).

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 coverage is 0%, so the description carries the full burden, yet it omits that the single 'rows' parameter is a JSON-encoded string (not an array of objects) and ignores the 12000-character cap. An agent could plausibly pass a native array and fail. Only 'collection of records' hints at the accepted shape.

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: converting a collection of records into aligned column arrays. The transformation direction is unambiguous. It does not explicitly distinguish itself from sibling converters like bpj_csv_to_json or bpj_json_to_csv, which prevents 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 when-to-use guidance, no prerequisite statement, and no named alternative among the many table/format-conversion siblings. An agent must infer that this is for pivoting wide records into columnar form from the name alone.

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.