Skip to main content
Glama

Add consecutive row numbers

bpj_table_row_numbers
Read-onlyIdempotent

Add a new ordinal field beginning at a specified positive row number.

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>",
      "target": "<target>",
      "start": "<start>"
    },
    "name": "bpj_table_row_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
startYes
targetYes

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?

The annotations already disclose that the operation is read-only, non-destructive, and idempotent, lowering the burden on the description. The description adds that the ordinal field starts at a specified positive number, but it does not clarify overwrite behavior for the target column, how rows are ordered, or what the output looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words. It is compact and easy to parse, even though brevity contributes to the semantic gaps noted elsewhere.

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 three-parameter table transformation with 0% schema description coverage and no output schema, the description is too thin. It leaves the rows input format, target-column behavior, and output expectations unexplained, which is inadequate for reliable 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 needs to carry parameter meaning. It gives some context for only two parameters: 'new ordinal field' relates to target and 'beginning at a specified positive row number' relates to start, while the required 'rows' parameter (a JSON record array) is never explained.

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: adding a new ordinal field beginning at a chosen positive row number. It is clear what the tool does, but it does not explicitly distinguish itself from sibling table-numbering tools such as bpj_table_bin_numbers or bpj_dq_whole_numbers.

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 guidance about when to use this tool versus alternatives, nor any stated prerequisites or exclusions. The use case must be inferred entirely from the one-sentence purpose statement.

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.