Skip to main content
Glama

Orthogonal vector projection

bpj_pairs_projection
Read-onlyIdempotent

Project the first vector onto the second and return both projection and orthogonal residual.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that two values come back (projection and orthogonal residual), which is genuinely useful given there is no output schema, but it omits computation constraints such as what happens with a zero-norm second vector or mismatched series lengths.

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 the operation and the return values, zero filler or repetition. It is arguably too terse for the gaps it leaves, but every word present earns its place.

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 tool with no output schema and 0% schema coverage, the description should explain the JSON string encoding of the inputs and the equal-length/non-zero-norm conditions. It describes the return shape adequately but leaves the agent guessing about input formatting and failure modes.

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 burden; it does clarify the crucial asymmetry that x is projected onto y, which is not derivable from the bare names 'x' and 'y'. However, it adds nothing about the fact that both parameters are JSON-encoded numeric series strings or about required length equality, leaving the format semantics to the schema titles alone.

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?

Names a specific operation and direction ('Project the first vector onto the second'), which distinguishes it from siblings like bpj_pairs_cosine or bpj_pairs_residual_diagnostics that consume the same pair of series but return different statistics. It is clear about what is computed, though it never explicitly contrasts itself with those siblings.

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, no mention of prerequisites (equal-length series, non-zero norm for the second vector), and no pointer to alternative pairwise tools. The only implicit usage signal is the projection direction stated in the sentence.

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.