Skip to main content
Glama

analyze_data_quality

Identify data-quality issues in a dataset and get recommendations to fix them.

Instructions

Report data-quality issues and recommendations.

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": "analyze_data_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDataset filename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/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, and it discloses almost nothing. 'Report' weakly implies a read-only operation, but the description does not say what issues are detected, whether recommendations are generated by rules or models, how costly the analysis is, or what the output looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is short and front-loaded with zero wasted words, but it is under-specified rather than concise. One more sentence about scope or output would have improved it without bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although the tool is simple (one required parameter, no nesting), there is no output schema, so the description should explain what a report contains. It does not, and it also omits any guidance on when the analysis applies, leaving the definition incomplete for an agent deciding whether to call it.

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% for the single 'name' parameter, so the schema already explains that it is a dataset filename. The description adds no meaning beyond that, which is acceptable given full coverage but earns only the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Report' and resource 'data-quality issues and recommendations' give a rough sense of the tool, but it reads as a one-line fragment rather than a precise statement of what is analyzed or produced. It does not differentiate itself from siblings like inspect_dataset or analyze_correlations, which an agent could easily confuse with 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 when-to-use guidance, no mention of prerequisites (e.g., dataset must be prepared or loaded), and no indication of when to prefer this over inspect_dataset or analyze_correlations. The agent is left to infer usage entirely from the name.

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