Skip to main content
Glama

Geometric mean of positive values

bpj_series_geometric_mean
Read-onlyIdempotent

Average positive multiplicative factors in logarithmic space.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, closed read operation, so the description only needs to add domain behavior. It does add the meaningful constraint that inputs are positive multiplicative factors and that the computation occurs in log space, but it omits what happens with zero or negative inputs (error vs. skip) and what magnitude/scale limits apply.

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 filler, and the key qualifier 'positive' appears early. It is arguably over-compressed rather than padded, so the structure itself is sound and the deficiency is coverage, not verbosity.

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 one-parameter math tool with no output schema, an agent still needs to know the return shape (a single scalar), the positivity precondition's failure mode, and the input encoding. None of these are supplied, so the description is not complete enough to call the tool confidently without inspecting the schema.

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 carries the full burden for the single 'values' parameter. It says nothing about the required JSON-array-in-a-string encoding, the 12000 character limit, or how many values are accepted, leaving the schema's terse title as the only clue.

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?

"Average positive multiplicative factors in logarithmic space" describes the geometric mean conceptually but never names the operation or states a verb+resource. It is understandable to a statistical reader yet does not distinguish this tool from siblings like bpj_series_harmonic_mean or bpj_series_root_mean_square, which are equally 'averages of a 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?

There is no guidance on when to choose a geometric mean over a harmonic or arithmetic mean, and no mention of the sibling alternatives. The only implicit usage constraint is that the factors must be positive, which is useful but not framed as a when/when-not rule.

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.