Skip to main content
Glama

find_issues

Read-only

Detect CSV data quality issues—disguised missing values, sentinel codes, high missingness, constant columns, duplicate rows, IQR outliers, and numbers stored as text—with severity and column.

Instructions

Find data quality issues (with severity and column): disguised missing values, sentinels like 999, >30% missing columns, constant columns, duplicate rows, IQR outliers and numbers stored as text.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so safety is covered. The description adds genuine value by stating that findings carry severity and column attribution, but it omits the detection thresholds beyond the one 30% example and says nothing about scan scope or cost on large datasets.

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 front-loaded sentence with the purpose first and the detection list after; every listed check is informative. The parenthetical '(with severity and column)' slightly interrupts the flow but adds real content.

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?

An output schema exists, so return structure need not be explained, and annotations cover the safety profile. The definition is still incomplete on the one thing an agent must get right to call it: what 'name' identifies and what unit the scan operates over.

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?

The single parameter 'name' has 0% schema description coverage, so the description carries the full burden and fails: it never says whether 'name' is a dataset, table, or file identifier. With one required and ambiguous parameter, this is a meaningful gap rather than a minor one.

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 specific verb and resource ('Find data quality issues') and enumerates exactly which checks run (disguised missing values, sentinels like 999, >30% missing, constant columns, duplicates, IQR outliers, numbers stored as text), so an agent knows precisely what class of finding to expect. It does not, however, distinguish itself from siblings such as profile_dataset or quality_score, which cover adjacent analytical ground.

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?

Usage is only implied by the enumeration of issue types; there is no explicit statement of when to prefer this over profile_dataset or quality_score, nor any exclusions. An agent can infer this is the diagnostics tool, but must guess the boundary with the profiling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.