Skip to main content
Glama

Empirical Shannon entropy

bpj_series_entropy
Read-onlyIdempotent

Compute the Shannon entropy in bits from observed value frequencies.

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

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context by specifying the output unit (bits rather than nats) and that the estimate is empirical (plug-in from observed counts), which implies sensitivity to sample size and zero-probability categories. It does not say whether the result is normalized or how ties/unique values are counted.

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?

One front-loaded sentence with no filler; the unit and computation are stated immediately. It is arguably under-sized for a parameter with a non-obvious wire format, but nothing in it is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-argument numeric utility with read-only annotations, most of what an agent needs is present: what is computed, the unit, and the estimation basis. The gap is that there is no output schema and the description does not reveal the expected JSON-string input encoding or the granularity at which distinct values are counted, so a caller can still get the invocation wrong.

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% and the single parameter is a string field requiring a JSON-encoded number array ('Number array (JSON)', maxLength 12000) — an unusual encoding the description never mentions. The phrase 'observed value frequencies' hints that the array is counted into distinct values, but the serialization format expected by the caller is undocumented in both the description and the schema.

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 verb and computation ('Compute the Shannon entropy in bits') plus the data basis ('from observed value frequencies'), which is far more precise than a bare name restatement. It does not explicitly distinguish itself from neighbours like bpj_series_histogram, bpj_series_gini or bpj_series_modes, which also derive quantities from value frequencies.

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 explicit when-to-use guidance, no stated prerequisites, and no named alternative for cases where a different dispersion or complexity measure is wanted. At best, 'observed value frequencies' implicitly signals that the input should be discrete/categorical data, but the agent must infer that.

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.