Skip to main content
Glama

Row completeness profile

bpj_dq_sparse_rows
Read-onlyIdempotent

For every row report missing columns and the fraction of fields filled in.

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

Input Schema

NameRequiredDescriptionDefault
rowsYes

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, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral value by stating the output granularity (per row) and the two reported metrics, but it says nothing about how the input JSON is validated or what happens on malformed rows.

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?

One sentence with no filler, and the scope ('For every row') is front-loaded ahead of the reported metrics. It is efficient, though the terseness is part of why the input format goes unexplained.

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 simple single-parameter read tool with rich annotations this is close to sufficient in terms of what is computed. With no output schema, however, the description should carry more of the return shape (e.g. keyed by row index? reported as objects or triplets?) and it leaves the input encoding entirely implicit.

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 the description never mentions the single parameter 'rows'. It does not explain that this is a serialized JSON array of record objects, nor that there is a 12,000-character ceiling — the schema title 'Record array (JSON)' carries that meaning alone, and the description does not compensate for the gap.

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?

States a specific verb ('report') and specific outputs ('missing columns' and 'the fraction of fields filled in') scoped per row, which is clear and concrete. It does not differentiate itself from near-neighbours such as bpj_dq_required_cells or bpj_dq_column_contract, so an agent must infer the boundary rather than read it.

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 when-to-use or when-not guidance, and no alternative tool is named. The 'for every row' phrasing weakly implies a row-level rather than column-level completeness check, which is the only usage signal present.

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.