Skip to main content
Glama

Population moment skewness

bpj_series_moment_skewness
Read-onlyIdempotent

Compute the third standardized central moment of the empirical population.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a safe, read-only, idempotent, closed-world computation, so the safety profile is covered. The description does add one genuinely useful behavioral detail by specifying 'empirical population', signalling no sample bias correction, but it is silent on degenerate inputs (constant series causing division by zero), minimum observations, and NaN/inf behavior.

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 no redundant wording or filler. It is efficient, though the terseness leaves no room for the operational detail an agent needs, so brevity here is close to under-specification.

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 at least indicate what is returned and its plausible range, which it does not. For a one-parameter math tool with strong annotations this is close to adequate, but the input format (values is a JSON-encoded number array string) and edge-case behavior remain undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With exactly one required parameter and 0% schema description coverage, the description carries the burden of explaining input semantics, and it provides no information about the expected input format.

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 states a precise statistical operation: the third standardized central moment of the empirical population. That is a specific verb-plus-resource definition that an agent can map to skewness, though it never uses the word 'skewness' and draws no explicit contrast with nearby siblings such as excess_kurtosis or median_absolute_deviation.

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 guidance at all: no indication of when population skewness is preferred over a robust or sample-based alternative, no prerequisites about series length or variability, and no mention of what the sibling tools would be used for instead. The agent must infer the calling context entirely from the name.

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.