Onepin

Configure quality checks

configure_quality_checks

DestructiveIdempotent

Change the quality policy on voice generators a saved workflow already has.

The server finds each branch and rewires every retry edge; you do not draw them. Use target to scope to ids or locales, and patch_workflow for a threshold on one node. Call without confirm for an edit_token, then again with confirm=true.

Input Schema

Name	Required	Description
`checks`	Yes	The checks to set. Types you do not list keep what they have, unless replace=true.
`target`	No	Which generators to change. Omit to change every one.
`confirm`	No	false changes nothing and returns what this would do. true applies it.
`replace`	No	true makes checks the WHOLE policy: types not listed are removed with their retries.
`edit_token`	No	From this tool's own unconfirmed reply. Proves the user approved replacing THIS graph; expires in 10 minutes.
`workflow_id`	Yes	The workflow_id from list_workflows. Never invent one.
`include_normalization`	No	true also puts text normalization in front of the generators this changes.
`pronunciation_remediation`	No	true builds a listed Pronunciation check as detect->correct->re-grade, not a retry.

Output Schema

Name	Required	Description	Default
`name`	No
`note`	No
`valid`	No
`errors`	No
`strike`	No
`blocked`	No
`warnings`	No
`next_step`	No
`configured`	No
`edit_token`	No
`console_url`	No
`workflow_id`	No
`pre_existing`	No
`changed_nodes`	No
`feature_offers`	No
`workspace_slug`	No
`nearest_feasible`	No
`workflow_summary`	No
`requires_confirmation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

changedInput schema / $defs / Precede / description

Previous value: -"Put a node immediately in front of this check, on the path it grades."New value: +"Settings for the Phoneme Injector this check is always built with."

changedInput schema / $defs / Precede / properties / with / description

Previous value: -"The node placed immediately before this check. Its wiring is the server's."New value: +"The node those settings are for. It is added either way."

Changed1 schema field changedOct 16, 2026

addedOutput schema / properties / feature_offers

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

First observedOct 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotent=true, so the safety baseline is set; the description adds genuinely non-obvious behavior — the server finds branches and rewires every retry edge itself, and the first call without confirm is a dry-run that yields an edit_token. It stops short of restating that replace=true removes existing checks and their retries, leaving that blast radius to the schema.

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

Conciseness5/5

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

Four short sentences, zero filler, purpose front-loaded before mechanism and routing. Every sentence contributes something an agent would not get from the structured fields alone.

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?

With an output schema present and full annotation coverage, the description needn't explain return values, and it handles the hardest part — the two-phase token protocol and server-side edge rewiring. A small gap remains for a destructive tool: it never warns in its own words that replace=true deletes unlisted checks, nor notes the ten-minute edit_token expiry.

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% and each of the eight parameters is already documented in-field (target, confirm, replace, edit_token, checks all have descriptions). The description adds only the sequencing semantics of confirm plus edit_token, restating the target scoping that the schema already explains. Baseline 3 is correct when the schema carries the load.

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

Purpose5/5

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

States a specific verb and resource ("Change the quality policy on voice generators") and scopes it to a saved workflow. The second sentence clarifies that this is a graph-level rewrite, not a hand-wired edit, and the third sentence names patch_workflow as the sibling for the narrower single-node case, so an agent can separate the two without reading either schema.

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?

Explicitly routes the agent: use target to scope by ids or locales, use patch_workflow instead when changing a threshold on one node. It also gives the mandatory confirm-then-edit_token sequence. What's missing is the when-not condition around replace=true clearing unlisted types, which only appears inside the schema field text.

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

All Onepin 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.

Resources

Need Help?