Skip to main content
Glama

Euclidean unit vector

bpj_series_unit_vector
Read-onlyIdempotent

Scale each component by the Euclidean norm of the vector.

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_unit_vector"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that: it does not say what happens when the norm is zero (division by zero / empty or all-zero input), nor what the return shape is for a scalar-returning or vector-returning operation.

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 short sentence with no filler, and the core operation is front-loaded. The only structural weakness is that the sentence is so terse it omits the division direction that would make the operation unambiguous.

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 simple one-parameter numeric transform with no output schema, the definition is minimally adequate. It still leaves the zero-norm edge case and the output format (scaled vector vs. norm) unstated, which matters for a normalization routine.

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 must carry the load, and it only partially does: 'each component' implies the single parameter is a numeric vector, but the JSON-encoded-string form and the 12000-character cap are left entirely to the schema's title and maxLength. Baseline of 3 reflects marginal added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete operation (scaling each component by the Euclidean norm), so the mathematical transformation is inferable. However, it is phrased as scaling *by* the norm rather than dividing by it, which reads as multiplication and only resolves to normalization via the title 'Euclidean unit vector'. It also gives no hint of how this differs from siblings like bpj_series_min_max_scale or bpj_series_center.

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 statement of when a different scaling tool in the large bpj_series_* family would be preferred, and no prerequisites. The agent must infer the use case purely from the math described.

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.