Skip to main content
Glama

Softmax score probabilities

bpj_series_softmax
Read-onlyIdempotent

Exponentiate scores after subtracting the maximum and normalize to probabilities.

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

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 readOnly, idempotent, non-destructive, so safety is covered. The description adds useful behavioral detail by explaining the max-subtraction for numerical stability, but it does not say that output probabilities sum to 1, preserve input length, or how they are returned.

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 tight sentence with no wasted words, front-loaded with the algorithm. It is appropriately sized for a simple math transform, though a clause on the input format would have earned its place.

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?

No output schema exists, so the description should clarify the return shape and the string-JSON input encoding; it does neither. The computational semantics are complete, but the invocation and result contract are not.

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 coverage is 0% for the single parameter, and the description never mentions it. Critically, the description does not say that `values` is a JSON-encoded string array rather than a native array, which is the main invocation hazard here.

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?

States the exact operation: exponentiate, subtract the max for numerical stability, then normalize to probabilities. That is specific enough to distinguish it from siblings like bpj_series_min_max_scale or bpj_series_cumulative_share, though it never names an alternative or states the resource is a numeric series.

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?

No guidance on when to use softmax versus other normalization or distribution tools, no prerequisites, and no mention of what the input should represent (raw scores, logits, arbitrary magnitudes). The agent must infer the use case entirely.

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.