Skip to main content
Glama

One-hot category indicators

bpj_table_boolean_indicators
Read-onlyIdempotent

Encode categories as binary columns and return the labels in first-seen order.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the operation read-only, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond that: labels are returned in first-seen order. It does not disclose whether original columns are preserved, how missing or unseen categories are handled, or the exact output shape.

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; the core operation and output ordering are stated immediately. It is tight, though its brevity leaves no room for the operational detail an agent needs.

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?

This is a data-transformation tool with no output schema and two undocumented parameters, and the description is one sentence. It omits the input encoding (rows as a JSON string), the output shape (do indicator columns replace or accompany the source column?), and null/empty-category behavior, all of which an agent needs to call 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?

Schema description coverage is 0%, so the description must carry parameter meaning, but it never mentions either parameter. It implies a categorical column exists but does not map that to the 'column' argument, nor does it explain that 'rows' is a JSON record-array string with a 12,000-character cap. Only the schema's bare titles ('Record array (JSON)', 'Column name') provide any signal.

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: 'Encode categories as binary columns,' which unambiguously identifies one-hot encoding, and the title reinforces it. It does not explicitly distinguish this transform from any sibling tool, so it falls 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 guidance, no prerequisites, and no named alternative among the many table tools. Usage is only weakly implied by 'Encode categories,' leaving the agent to infer the scenario on its own.

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.