Skip to main content
Glama

Value shares within groups

bpj_table_group_percent_of_total
Read-onlyIdempotent

Compute each nonnegative observation’s fraction of its group total, returning null shares for zero-total groups.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes
groupYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the useful edge behavior that zero-total groups return null shares and that observations are expected to be nonnegative, but it does not cover missing values, negative inputs, or output shape.

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 description is a single efficient sentence. It front-loads the core computation and then adds the zero-total edge case without wasted wording.

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 three-parameter grouping computation with no schema descriptions and no output schema, the description is too sparse. It clarifies the core operation and one edge case but omits input format details, parameter meanings, and expected return structure beyond null shares.

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% for all three required parameters. The description does not explain the expected JSON structure of the rows parameter, the role of the group column, or how the column parameter selects the value to compute shares for, so it leaves the parameters under-specified.

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 computation: it computes each nonnegative observation's fraction of its group total. The resource and scope are clear, but it does not explicitly distinguish this from similar group-total or running-total siblings.

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 description implies usage by assuming nonnegative observations and explaining zero-total group behavior, but it gives no explicit guidance on when to choose this tool over alternatives such as bpj_table_group_total or bpj_table_group_running_total.

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.