Data Quality Gate

get_checked_original_download

Read-onlyIdempotent

Get the authenticated original-data download path after continue, while the 24h source retention remains. SHA256 identifies the actual checked bytes; never forward report JSON as customer 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": {
      "job_id": "<job_id>"
    },
    "name": "get_checked_original_download"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish this as a safe, idempotent read, so the description's added value is the 24-hour source-retention expiry and the authentication requirement — both behavioral facts the schema doesn't carry. The SHA256 note clarifies data provenance. It stops short of saying what happens once retention lapses (error vs. missing path), leaving one operational gap.

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 tight sentences with no filler; the retrieval purpose and the retention constraint are front-loaded. Minor cost is the undefined 'after continue', which forces interpretation of a key precondition.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, the description covers what is returned (a download path for the checked original), provenance (SHA256), the time limit, and a misuse warning. It is nearly complete; only the post-expiry behavior and the meaning of the 'continue' step are unaddressed.

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?

The single parameter job_id has 0% schema description coverage, and the description adds nothing about its meaning, source, or format. A job identifier is fairly self-evident and likely obtainable from the sibling check tools, so this is a moderate rather than severe gap.

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?

States a specific verb and resource: 'Get the authenticated original-data download path'. This is clearly distinct from the sibling quality-check/report tools, and the mention of checked bytes ties it to the quality-check workflow. The phrase 'after continue' is jargon that isn't defined, which keeps it from a 5.

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?

Implies the usage window ('after continue, while the 24h source retention remains') and warns against forwarding report JSON as customer data, which is a useful use-case constraint. However, it never names an alternative for fetching the report/summary data, so the agent must infer where to go for non-original outputs.

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

All Data Quality Gate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.