Skip to main content
Glama

Destroy a release-policy checker

destroy_checker
DestructiveIdempotent

Destroy one of an organization's own checkers by name. Valet stops sending release files to its URL. Confirm with the user first. A checker that a release policy names is refused: the answer names the policies, so destroy_policy them first, or point them at another checker with set_policy. Destroying a checker that is already gone changes nothing. Requires connecting a Valet account. Requires the Admin role.

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": {
      "checker": "<checker>"
    },
    "name": "destroy_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkerYesThe checker's name, such as org:snyk as list_policies reports it, or snyk.
org_nameNoThe Valet organization the checker belongs to. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
kindYesAlways checker: the kind of thing this tool destroys.
nameYesName of the checker destroyed, always with its org: prefix, as a policy spells it.
already_goneNoTrue when the checker was already gone before the call, so nothing was destroyed. Absent when this call destroyed it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / already_gone / description
      Previous value: -"True when the thing was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."New value: +"True when the checker was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."
    • changedOutput schema / properties / kind / description
      Previous value: -"What the thing was, such as channel, connector, or resource."New value: +"Always checker: the kind of thing this tool destroys."
    • addedOutput schema / properties / kind / enum
      Added value: +[
      +  "checker"
      +]
    • changedOutput schema / properties / name / description
      Previous value: -"Name of the thing the call destroyed, as the caller gave it."New value: +"Name of the checker destroyed, always with its org: prefix, as a policy spells it."
  2. Changed5 schema fields changed
    • changedInput schema / properties / checker / description
      Previous value: -"Required. The checker's name, such as org:snyk as list_policies reports it, or snyk."New value: +"The checker's name, such as org:snyk as list_policies reports it, or snyk."
    • addedOutput schema / properties / already_gone / description
      Added value: +"True when the thing was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."
    • addedOutput schema / properties / kind / description
      Added value: +"What the thing was, such as channel, connector, or resource."
    • addedOutput schema / properties / name / description
      Added value: +"Name of the thing the call destroyed, as the caller gave it."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "already_gone": {
      +      "type": "boolean"
      +    },
      +    "kind": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "org": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "name",
      +    "kind"
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, but the description goes well beyond them: it states the real-world effect (Valet stops sending release files to the URL), the referential-integrity refusal and that the error names the blocking policies, the idempotent no-op, and two hard prerequisites (connected Valet account, Admin role). The only shortfall is that it does not describe what the success response contains, which the output schema covers.

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?

Front-loaded with verb and resource, then the confirmation requirement, the failure path and its remedies, the idempotency note, and the prerequisites last. Every sentence carries distinct operational information with no repetition of the title or annotations.

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

Completeness5/5

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

For a destructive, org-scoped tool it covers consequences, confirmation, referential-integrity failure and recovery, idempotency, and auth/role prerequisites. With an output schema present and full schema coverage, nothing an agent needs to call this safely is missing.

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%, including the 'org:snyk or snyk' naming format and the org_name default, so the schema already carries the parameter burden. The description reinforces that the checker is org-scoped, but adds no new format, validation, or resolution detail beyond the schema. Baseline 3 applies.

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?

The opening sentence pairs a specific verb (Destroy) with a specific resource (one of an organization's own checkers) and adds the resolution key (by name). That scoping phrase 'organization's own' plus the named follow-on tools (destroy_policy, set_policy) let an agent distinguish this from set_checker and other destroy_* siblings without inspecting schemas.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('Confirm with the user first'), an explicit refusal case with the remedy routed to two named alternatives (destroy_policy first, or re-point with set_policy), and an explicit no-op case (destroying an already-gone checker changes nothing). An agent knows exactly when this call will fail and what to do instead.

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