Skip to main content
Glama

Gini coefficient

bpj_series_gini
Read-onlyIdempotent

Measure inequality for a nonnegative series using the Lorenz trapezoid areas.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds a genuine domain constraint (input must be nonnegative) and discloses the computational approach (Lorenz trapezoid areas), but says nothing about edge cases such as all-zero or constant series where the coefficient is undefined.

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 well-formed sentence with no filler, front-loading the operation before the method. It is efficient, though terse enough that it omits structure an agent would benefit from.

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?

For a one-parameter statistical tool with annotations but no output schema, the description should at minimum state the return type and range (a scalar in [0,1]) and edge-case behavior. As written it covers the core computation but leaves those gaps for the agent to infer.

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

Parameters3/5

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

Schema coverage is 0%, so the schema only reveals that 'values' is a JSON number array string capped at 12000 characters. The description compensates partially by imposing the nonnegativity constraint, but says nothing about encoding, ordering, minimum length, or zero handling.

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 operation (measure inequality) with a named method (Lorenz trapezoid areas), which implicitly identifies the Gini coefficient and partially separates it from the sibling bpj_series_lorenz. It never names the statistic outright or states that it returns a single normalized index, so differentiation from siblings is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for a nonnegative series' implicitly states a precondition and therefore when not to use it, but there is no explicit routing to alternatives such as bpj_series_lorenz or bpj_series_relative_spread, and no statement about what to do with negative values.

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.