Skip to main content
Glama

Standardize worksheet columns

bpj_matrix_column_standardize
Read-onlyIdempotent

Center and scale each column using its population spread, mapping constant columns to zero.

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": {
      "matrix": "<matrix>"
    },
    "name": "bpj_matrix_column_standardize"
  }
}

Input Schema

NameRequiredDescriptionDefault
matrixYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description earns credit for disclosing behavior the annotations do not: it specifies population spread (implying a ddof=0 denominator rather than sample) and states the edge-case rule that constant columns map to zero. It does not describe the returned structure, which keeps it from a 5.

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?

A single sentence with the operation front-loaded and the two essential specifics—population spread and the constant-column rule—packed in without waste. Nothing is redundant with the tool name.

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 one-parameter pure transform with full annotation coverage and no output schema, the description covers the core computation and one important edge case. It is still missing what the output looks like (shape and structure of the standardized matrix) and any input format expectations, which matter for a no-output-schema tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 burden, but it only implies the input is column-structured via 'each column'. It does not explain the expected JSON encoding, shape constraints, or the 12,000-character limit that the schema enforces, so the agent must rely on the schema's bare title.

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 definition names a specific verb and resource ('Center and scale each column') and adds a precise mechanism ('using its population spread'), so an agent knows this is a column-wise standardization transform rather than a covariance, norm, or transpose operation. It does not explicitly differentiate itself from the many matrix siblings, which keeps it 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 statement of when to use this tool rather than a sibling such as bpj_matrix_norms or bpj_matrix_column_covariance, and no prerequisites or exclusions are given. The only guidance is implied by the phrase 'Center and scale', which leaves the agent to infer the use case.

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.