Skip to main content
Glama

Population excess kurtosis

bpj_series_excess_kurtosis
Read-onlyIdempotent

Subtract three from the fourth standardized central moment.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description would need to add computational context. It does not mention the population-vs-sample distinction (which the title implies but the description drops), minimum series length required for a fourth moment, or handling of empty/constant series.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, so it is concise, but it is terse to the point of under-specification and leads with a formula instead of the operation and its input.

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 numeric tool with no output schema and no behavioral annotations beyond safety flags, the description should at minimum state the input format, the population definition, and edge-case behavior. None of these are present, leaving the agent to guess at invocation details.

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% for the single parameter, and the description never mentions it. The critical detail that 'values' must be a JSON-encoded string of numbers (maxLength 12000) rather than a native array is only weakly conveyed by the schema's title, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence 'Subtract three from the fourth standardized central moment' is a formula restatement of the title 'Population excess kurtosis' rather than a statement of what the tool does to what input. It never says it operates on a supplied series of numbers, so an agent must infer the verb+resource from the title alone.

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, no mention of when excess kurtosis is preferable to alternatives, and no reference to sibling statistics tools such as bpj_series_moment_skewness or bpj_series_relative_spread. Usage is entirely left to inference from the tool 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.