Skip to main content
Glama

Tied modes and counts

bpj_series_modes
Read-onlyIdempotent

Return all values tied for highest frequency and their shared count.

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

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful return-shape context — that results come back as a set of tied values plus one shared count, implying multiple results are possible — but says nothing about tie handling edge cases (all-unique input, empty input) or how the string input is interpreted.

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?

A single front-loaded sentence with no filler; the defining condition (tied for highest frequency) and the output (values plus shared count) both appear immediately.

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 read-only statistic, the core semantics are present and no output schema exists that would need explaining. However, the input serialization format and the degenerate-case behavior are unaddressed, so an agent still lacks the full picture needed to call it confidently.

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 there is exactly one required parameter, yet the description never mentions it. The schema's own title hints that values is a JSON-encoded number array passed as a string with a 12000-char cap, but the description does not reinforce, explain, or give an example of that encoding, leaving the agent to rely entirely on the title.

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 names a precise operation: returning every value tied for highest frequency plus the shared count, which unambiguously identifies a multi-modal computation. No sibling in the supplied list performs this operation, so there is little ambiguity to resolve, but the description does not explicitly distinguish itself from neighbours like the quantile/histogram tools.

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?

It states what the tool computes but gives no when-to-use guidance, no prerequisites, and no pointer to any alternative (e.g. histogram or quantile tools) for related but different questions. The usage is implied by the operation name only.

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.