Skip to main content
Glama

Weighted Decision Matrix

bpj_weighted_choice
Read-onlyIdempotent

Rank alternatives against weighted criteria. Enter each row in the same criterion order.

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": {
      "criteria": "<criteria>",
      "options": "<options>"
    },
    "name": "bpj_weighted_choice"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsYes
criteriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish that this is a safe read-only, idempotent, non-destructive operation, so the description need not repeat that. The description adds that the tool ranks alternatives and requires rows to align with criterion order, but it omits output format, tie handling, and how weights are applied.

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?

The definition is two short sentences with the purpose front-loaded and no wasted wording. It is concise, though its brevity contributes to the missing behavioral and parameter detail.

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 that accepts two complex string-encoded inputs and produces a ranking, the description is incomplete. There is no output schema and no explanation of how weights are normalized, how ties are resolved, or what the ranked result looks like.

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%, and the description does not explain the required 'Criterion|weight' or 'Option|scores' formats, score ranges, or limits beyond the schema titles. It adds only the relational rule that each option row must match the criterion order, which does not fully compensate for the missing parameter semantics.

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: rank alternatives against weighted criteria. This clearly identifies a weighted decision-matrix computation, though it does not distinguish the tool from sibling analysis or matrix-preview tools.

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 use this tool versus alternatives, nor any prerequisites or exclusions. The only usage instruction is a data-entry rule about row ordering.

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.