Skip to main content
Glama

data_quality_log

Review data-quality issues found while cleaning hospital tables, including row counts, causes, and fixes; filter by dataset name to inspect one table's log.

Instructions

The 53 problems found while cleaning: what was wrong, how many rows, what was done, how it was found. Pass dataset (e.g. "uk.spells", "ke.bed_state") to see one table's issues, or part of a name such as "uk".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_quality_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the content of each logged problem, which is genuinely useful, but says nothing about ordering, volume, or behavior when no dataset is passed, and the strange '53' figure is unexplained. An output schema exists, which covers the return shape, keeping this at a moderate rather than low score.

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?

Two sentences, front-loaded with what the log contains, then the filtering instruction. Nearly every clause earns its place; the only weak element is the unexplained '53', which adds noise rather than information.

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 single-optional-parameter read tool with an output schema documenting returns, the description covers purpose and filter semantics adequately. The remaining gap is the no-argument case: it is only inferable that omitting `dataset` returns issues across all tables.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does: it names the parameter, gives two concrete dataset examples ('uk.spells', 'ke.bed_state'), and reveals substring/prefix matching ('or part of a name such as "uk"'), a behavior not expressible in the schema. It stops short of saying what an omitted dataset returns.

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 the resource precisely: a log of data-cleaning problems with four named fields (what was wrong, rows affected, what was done, how it was found). The verb is implicit ('the problems found while cleaning' rather than 'retrieve'), and the hardcoded '53' reads as an odd artifact, but an agent can still tell this is the data-quality issue log and not describe_table, list_tables, overview, or query.

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: the agent is told to pass `dataset` to see one table's issues, which suggests the tool exists for inspecting cleaning problems. There is no explicit when-to-use or when-not-to-use guidance relative to the siblings (e.g. use describe_table for schema, this for data-quality findings), so the routing decision is left to inference.

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