Skip to main content
Glama
Sign In

Data Quality Gate

by ai.contentsweep
OverviewDiscussionsAdmin

approve_quality_baseline

Idempotent

Approve the reviewed exact baseline hash for its specific contract after operator authorization.

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": {
      "baseline_id": "<baseline_id>",
      "expected_hash": "<expected_hash>",
      "approve": "<approve>"
    },
    "name": "approve_quality_baseline"
  }
}

Input Schema

NameRequiredDescriptionDefault
approveYes
baseline_idYes
expected_hashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is largely covered. The description adds real context beyond that — approval is gated on operator authorization and on the baseline having been reviewed, and it is bound to a specific contract — but it does not say what approval unlocks, whether it can be revoked, or what a rejection/failure 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.

Conciseness4/5

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

One front-loaded sentence with no filler; the verb and object lead. It is tight, though its brevity is part of why parameter and behavioral detail are missing.

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?

For a three-parameter, fully required mutation tool with no output schema and zero documented parameters, this single sentence leaves substantial gaps: the role of expected_hash, the meaning of the approve boolean, and the effect of a successful approval are all unstated.

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

Parameters2/5

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

Schema description coverage is 0% for all three required parameters, so the description carries the full burden and does not meet it. It gestures at 'exact baseline hash' (likely expected_hash) and 'specific contract' (which is not even a parameter), but never explains that expected_hash is presumably a concurrency/exactness guard, nor why an approve tool needs a boolean 'approve' flag.

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?

A specific verb (Approve) applied to a specific resource (a reviewed exact baseline hash) scoped to a contract, which separates it reasonably from the sibling approve_quality_contract. It could be sharper about how 'baseline' differs from the 'contract' being approved, but the intent is legible.

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?

The phrase 'after operator authorization' and 'reviewed' imply preconditions (the baseline must be drafted and reviewed, and an operator must have authorized it), which is useful guidance. However, it never says when NOT to use this tool or points to the sibling approve_quality_contract as the alternative path, so usage context is only implied.

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 toolsInspect
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.

Resources