Skip to main content
Glama

Bin a numeric field by cut points

bpj_table_bin_numbers
Read-onlyIdempotent

Assign zero-based interval indices using strictly increasing cuts, placing ties in the higher bin.

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>",
      "cuts": "<cuts>",
      "target": "<target>"
    },
    "name": "bpj_table_bin_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutsYes
rowsYes
columnYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: indices are zero-based and ties are placed in the higher bin, which determines the actual output values. It stops short of 5 because it says nothing about values falling outside the cut range or about null/non-numeric input handling.

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 dense sentence with no filler, and the core semantics (zero-based indexing, tie rule) are front-loaded. It is efficient, though the terseness borders on under-specification for a four-parameter tool.

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 read-only, idempotent table transform with no output schema, the description covers the output semantics reasonably (zero-based indices, tie placement). However, with 0% parameter description coverage and no explanation of the rows JSON format, target column behavior, or out-of-range handling, an agent still has to guess at invocation details.

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% across four required parameters, so the description must carry the burden and largely does not. It only clarifies that 'cuts' are strictly increasing, which is already implied by the schema title 'Ascending cut points'; the meaning and format of 'rows' (a JSON record array), 'column', and 'target' are left entirely unexplained.

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 names a specific operation on a specific resource: assigning zero-based interval indices to values using strictly increasing cut points. Along with the title ('Bin a numeric field by cut points'), an agent can tell this is a binning/quantization tool. It does not, however, distinguish itself from adjacent siblings such as bpj_table_numeric_sort or bpj_table_row_numbers, 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 when-to-use guidance, no prerequisites, and no mention of an alternative (e.g. when to sort/index rather than bin). The only constraint given, that cuts must be strictly increasing, is a validity rule rather than usage guidance.

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.