Skip to main content
Glama

Most frequent values by group

bpj_table_group_mode
Read-onlyIdempotent

Retain all tied most frequent target values within each group.

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": {
      "rows": "<rows>",
      "group": "<group>",
      "column": "<column>"
    },
    "name": "bpj_table_group_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and mutation behavior are covered. The description adds useful behavior about tie handling by retaining all tied most frequent values, but it does not explain return shape, row format, or error behavior.

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?

The description is a single front-loaded sentence with no filler. It is concise, though its brevity leaves important usage and parameter details unspecified rather than merely avoiding verbosity.

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 3-parameter tool with no output schema and 0% schema description coverage, the one-sentence description is too thin. It omits the input row format, output behavior, and practical guidance an agent would need to invoke it correctly.

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 carries the burden of explaining the three required parameters. It mentions the grouping concept and target values, but does not explain the rows JSON format, column reference syntax, or how group and column interact.

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 operation: retaining all tied most frequent target values within each group. This is clear as a grouped mode operation, but it does not explicitly distinguish the tool from the sibling bpj_table_group_value_frequency or similar group 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 only states what the tool does, with no when-to-use guidance, no exclusions, and no mention of alternatives. An agent must infer the appropriate context from the name and title alone.

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.