Skip to main content
Glama

Vector distance profile

bpj_pairs_distance_profile
Read-onlyIdempotent

Report Manhattan, Euclidean and Chebyshev distances between two aligned vectors.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "bpj_pairs_distance_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

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=true, idempotentHint=true, closed-world and non-destructive, so the safety profile is covered. The description adds the word 'aligned', hinting at a length/ordering constraint between x and y, but says nothing about validation failures, output shape, or what happens with mismatched lengths. Small added value beyond annotations earns a 3.

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 zero filler, listing the three metrics compactly. It is efficient but arguably under-sized for a tool whose inputs are opaque JSON strings.

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?

With no output schema, the description should indicate the shape of the result (three named distance values) and error behavior for unequal-length series; neither is stated. It is minimally adequate for a simple two-parameter read-only computation, but leaves return-format and failure-mode questions unanswered.

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 must compensate, and it only partially does: 'two aligned vectors' conveys positional pairing, but it never mentions that x and y are JSON-encoded numeric strings (per the schema titles), the 12000-character limit, numeric-validity requirements, or whether order affects the result (it does not for these symmetric metrics).

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 names a specific verb ('Report') and three concrete resources (Manhattan, Euclidean, Chebyshev distances) over a defined input ('two aligned vectors'), so an agent knows exactly what computation happens. It does not explicitly contrast itself with metric siblings such as bpj_pairs_cosine or bpj_pairs_spearman, so differentiation relies on the metric names alone.

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 choose this distance profile over related pair-metric tools (cosine, correlation, error metrics), nor any stated precondition beyond the phrase 'aligned vectors'. Usage is only implied by the metric names; exclusions and alternatives are absent.

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.