Skip to main content
Glama

Subtract aligned numeric fields

bpj_table_difference_column
Read-onlyIdempotent

Create a new field with the rowwise difference of two numeric columns.

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>",
      "subtract": "<subtract>",
      "target": "<target>"
    },
    "name": "bpj_table_difference_column"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes
targetYes
subtractYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only "rowwise", and says nothing about the subtraction direction, behavior on nulls or non-numeric values, or whether the source columns are preserved in the returned data. For a transformation tool with zero schema coverage, that is a thin disclosure.

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. It is efficiently written, though the brevity reflects under-specification rather than disciplined economy.

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?

With four required parameters, no output schema, and no parameter descriptions, the one-sentence description is not sufficient to call the tool confidently. It omits the row-input format, operand direction, and error behavior for non-numeric or missing values.

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 carries the full burden, yet it never maps its wording to the actual parameters (rows, column, subtract, target). Critically, it does not establish the operand order (presumably column minus subtract) or that rows is a JSON record array, leaving four required parameters semantically ambiguous.

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 specific verb and result ("Create a new field with the rowwise difference of two numeric columns"), which is far more informative than the name alone and tells an agent exactly what output to expect. It does not differentiate from nearby siblings such as bpj_sheet_subtract or bpj_trial_balance_difference, which also compute differences.

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 on when to use this versus the sibling subtraction tools, and no stated preconditions such as both columns being numeric or aligned row-by-row. An agent must infer the appropriate context entirely from the name and the word "numeric".

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.