Skip to main content
Glama

Complete-case record selection

bpj_table_complete_cases
Read-onlyIdempotent

Keep rows complete across selected fields and report the number omitted.

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>",
      "columns": "<columns>"
    },
    "name": "bpj_table_complete_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely behavioral fact beyond that — the number of omitted rows is reported — but leaves critical semantics unstated, notably what counts as 'incomplete' (null, empty string, zero, missing key) and whether row order or types are preserved.

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?

A single tight sentence with no filler, and the core operation is front-loaded. The brevity is nearly a virtue, though the same sentence would cost little more and buy much by defining 'complete'.

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?

The tool is simple — two required parameters, no output schema, safety already covered by annotations — so a short description is defensible. Still, the definition of missingness and the shape of the result (retained rows plus an omitted count) are the two things an agent most needs and neither is stated.

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 two parameters. 'Selected fields' gives indirect meaning to `columns` as the set of fields checked for completeness, but nothing clarifies that both parameters are JSON-encoded strings, nor what `rows` must contain. The compensation for the coverage gap is only partial.

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 — keeping rows that are complete across selected fields, plus reporting how many rows were omitted. This is a coherent operation an agent can distinguish from filling siblings such as forward_fill or coalesce. It stops short of naming any sibling explicitly, so it is clear but not sibling-differentiated.

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 guidance on when to use this versus alternatives like bpj_table_forward_fill, bpj_table_backward_fill, or bpj_table_coalesce, which handle the same missing-data problem differently. Usage is only implied by the phrase 'keep rows complete', with no preconditions, exclusions, or recommended context.

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.