Skip to main content
Glama

Data-quality rules generator

submit_dq_rules_generator
Idempotent

Infer per-column data-quality rules from a sample and generate a test module plus a rules file. When a new dataset needs baseline quality checks. Do not choose this when rules must be authored against a specification, not inferred. Example requests: Generate data-quality rules from this sample. | What checks should I run on this dataset? | Create a rules file and tests for this data.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_dq_rules_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the safety profile (non-read-only, idempotent, non-destructive, closed-world), so the description is not obligated to repeat that. It does add the useful behavioral fact that two artifacts are produced (test module plus rules file), but it is silent on the priced/quote authorization flow and what the job does with the sample, which are the operationally significant behaviors here.

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?

Compact and front-loaded: capability, trigger, exclusion, then example phrasings. The lone drawback is that the trigger is a sentence fragment and the example-request list is somewhat optional padding, though it does help surface natural-language invocations.

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 values need no explanation, and the input schema is well documented. However, this is a priced asynchronous capability whose workflow (quote, authorize, submit) is entirely absent from the description, leaving the agent to infer the job lifecycle from parameter names alone.

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 75%, and the schema itself already explains sample, quote_id, accepted_price, and authorized_by in detail. The description adds no parameter-level meaning at all, so it neither compensates for the uncovered portion nor extends what the schema says. Baseline 3 is appropriate for a schema that does most of the work.

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 specific verbs and artifacts: inferring per-column data-quality rules from a sample and generating both a test module and a rules file. That is far more concrete than its siblings' names alone, and the exclusion (not for specification-driven rule authoring) hints at the boundary with the validation/dbt-test siblings. It stops short of naming those siblings explicitly, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a positive trigger ('when a new dataset needs baseline quality checks') and an explicit negative condition ('do not choose this when rules must be authored against a specification, not inferred'). What is missing is a direct pointer to the alternative tool to use in that case, which would make routing unambiguous among the many data-quality siblings.

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.

Resources