Skip to main content
Glama

Min-max normalization

bpj_series_min_max_scale
Read-onlyIdempotent

Map the minimum to zero and maximum to one using a linear transformation.

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": {
      "values": "<values>"
    },
    "name": "bpj_series_min_max_scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered without prose. The description adds the behavioral detail that the mapping is linear and anchored at exact min/max, which implies sensitivity to outliers and undefined behavior for a constant series, but it does not state that edge case or describe what the call returns. With annotations carrying the safety burden, this is adequate but thin.

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?

One sentence, front-loaded with the operation and the resulting scale, with no filler or redundancy. Nothing could be removed without losing meaning.

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 one-parameter transform with no output schema, the description should at least confirm the input encoding and the shape of the result, and it does neither. It also omits the constant-series edge case that would make min-max division undefined, leaving real gaps on a tool that is otherwise simple.

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% for the single parameter, so the description should compensate but says nothing about it. The schema title 'Number array (JSON)' hints that values is a JSON-encoded array string with a 12000-character cap, yet the description never confirms the input is JSON-serialized text rather than a native list, which is a real invocation pitfall.

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-resource statement of the transformation ('map the minimum to zero and maximum to one using a linear transformation'), which is unambiguous about what the tool computes. It does not differentiate from nearby siblings such as bpj_series_robust_scale or bpj_series_center, so an agent cannot tell from the text alone which scaling variant to pick.

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 or when-not-to-use guidance and no mention of alternatives like robust scaling. The only implicit guidance is that the input should be a series to be rescaled; nothing tells the agent under what conditions min-max is preferred over the sibling scalers.

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.