Skip to main content
Glama

Equal-width histogram

bpj_series_histogram
Read-onlyIdempotent

Count observations in equal-width bins, including the maximum in the final bin.

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>",
      "bins": "<bins>"
    },
    "name": "bpj_series_histogram"
  }
}

Input Schema

NameRequiredDescriptionDefault
binsYes
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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds a meaningful boundary rule, that the maximum is included in the final bin, but it does not explain minimum inclusion, empty input, all-equal values, or what the returned counts look like.

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

Conciseness5/5

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

The definition is a single front-loaded sentence with no wasted wording, and the important maximum-bin edge case is stated directly. Its brevity is appropriate for the amount of information it chooses to convey.

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?

This is a relatively simple two-parameter tool with full safety annotations, but it has no output schema and 0% schema description coverage. The description covers the core operation and one edge case, yet omits how bin edges are computed, how malformed or empty JSON arrays are handled, and the shape of the result.

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 needs to compensate, but it adds almost no parameter meaning. It does not clarify that `values` is a JSON-encoded number array string with a length limit, nor that `bins` is constrained to 1-64, even though the schema titles provide only minimal hints.

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 specific verb and resource: counting observations into equal-width histogram bins. That is clear enough to distinguish it from calendar-weekday or UTF-8 byte histogram siblings, although it does not explicitly name the numeric-series scope or a sibling alternative.

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 use this histogram versus other histogram tools, nor any prerequisites or exclusions. The description only defines the operation itself, leaving tool selection entirely to inference.

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.