Skip to main content
Glama

analyze_data_quality

Read-only

Identify data quality issues by analyzing a table for completeness, duplicates, and stale records using configurable required fields and staleness thresholds.

Instructions

Analyse data quality for a table — completeness, duplicates, stale records

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

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
tableYesTable to analyse
days_staleNoConsider records stale after N days without update (default 180)
required_fieldsNoComma-separated fields that should be populated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. First observedv1.0.2

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description doesn't contradict it. The description adds only the set of quality dimensions inspected; it says nothing about scan cost on large tables, whether results are sample-based, or how findings are surfaced, which is the remaining behavioral value it could have contributed.

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 em-dash-delimited sentence that front-loads the purpose and appends the dimensions checked, with no filler. It is efficient, though it is arguably over-terse for a tool with four parameters and an async mode.

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 a read-only analysis with a fully documented four-parameter schema and no output schema. Since no output schema exists, the description should hint at what an agent receives back (per-dimension findings, scores, or row samples), and it does not, leaving a meaningful gap for a tool whose entire value is its result shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including defaults (days_stale=180) and the async/get_job polling contract, so the schema carries the parameter burden and the baseline of 3 applies. The description's mention of completeness, duplicates, and stale records loosely maps to required_fields and days_stale but adds no syntax, format, or constraint detail beyond the schema.

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 gives a specific verb ('Analyse') and resource ('data quality for a table') and enumerates the three dimensions checked: completeness, duplicates, stale records. It does not, however, differentiate itself from the sibling check_table_completeness, which an agent could plausibly confuse with the completeness dimension mentioned here.

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, when-not-to-use, or alternative-tool guidance. The listed checks imply the tool is for profiling a table, but an agent is left to infer that on its own, with no mention of when check_table_completeness or list_data_sources would be the better call.

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

Deploy Server

Other Tools