Skip to main content
Glama

Add or replace an organization checker

set_checker
DestructiveIdempotent

Add an organization checker, or replace the one with the same name. A checker is the organization's own HTTPS endpoint that implements Valet's Checker API. Once saved, a release policy can run it as org:: set_policy with that checker. Valet calls the endpoint's describe operation before saving and saves nothing if the call fails.

Saving a checker agrees, for the organization, to send the release files the endpoint asks for (the source, the build, or both) to the URL, for every release that a policy naming the checker evaluates. Once fetched, the files are outside Valet's control. Confirm that with the user before you call this tool. The answer names the files the endpoint asked for; those become the approved files. An endpoint that later asks for more is unavailable until the checker is saved again.

A credential header (Authorization, Cookie, X-Api-Key, or a name holding token, secret, key, or auth) takes exactly one {{NAME}} reference to a secret env var of the organization, after at most a scheme word, such as {"Authorization": "Bearer {{SNYK_TOKEN}}"}; any other text in it is refused. Valet resolves the reference at each call. Other headers are stored and listed as written, and a value in one that looks like a credential, such as a provider key or a URL with a user name, is refused. Have the user set the variable first with valet env set SNYK_TOKEN=... --org <org>, so the value never passes through this conversation. A reference to a variable that is not a secret of the organization is refused. list_policies shows the organization's checkers. 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>",
      "url": "<url>"
    },
    "name": "set_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWhere the organization's checker service listens, such as https://checks.example.com/snyk. Valet calls /v1/describe and the other Checker API paths under it, so give the base, not a full path.
checkerYesWhat to call the checker, such as snyk, so a policy can name it: set_policy runs it as org:snyk, the prefix marking a checker the organization added. Saving under a name already in use replaces that checker.
headersNoThe credential and any other headers the endpoint expects on Valet's calls, as header name to value, such as Authorization to Bearer {{SNYK_TOKEN}}, where SNYK_TOKEN is the organization's secret holding the token.
org_nameNoThe Valet organization that owns the checker. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
urlYesThe endpoint's base URL as saved.
fieldsYesThe settings a policy can give this checker, as the endpoint's describe operation reports them. Empty when it takes none.
inputsYesThe release files the endpoint asked for and this save approved: source, build, or both. Valet sends them to the URL for every release a policy naming this checker evaluates. Empty when it asked for none.
checkerYesThe checker's name as a policy spells it, such as org:snyk. Pass it to set_policy as checker.
headersYesHeaders Valet sends on every call, by name. A credential header shows its {{NAME}} reference, never a value. Empty when there are none.
descriptionYesWhat the checker does, as the endpoint's describe operation reports it. Empty when the endpoint declares none.
display_nameYesThe name a person reads, as the endpoint's describe operation reports it. Empty when the endpoint declares none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / headers / description
      Previous value: -"What the endpoint needs to accept Valet's calls, usually its credential, as header name to value, such as Authorization to Bearer {{SNYK_TOKEN}}. Valet sends them on every call."New value: +"The credential and any other headers the endpoint expects on Valet's calls, as header name to value, such as Authorization to Bearer {{SNYK_TOKEN}}, where SNYK_TOKEN is the organization's secret holding the token."
  2. Changed3 schema fields changed
    • changedInput schema / properties / checker / description
      Previous value: -"The checker's name, such as snyk. A policy runs it as org:snyk, the org: prefix marking a checker the organization added. Saving an existing name replaces that checker."New value: +"What to call the checker, such as snyk, so a policy can name it: set_policy runs it as org:snyk, the prefix marking a checker the organization added. Saving under a name already in use replaces that checker."
    • changedInput schema / properties / headers / description
      Previous value: -"Headers Valet sends on every call to the endpoint, as name to value, such as Authorization to Bearer {{SNYK_TOKEN}}."New value: +"What the endpoint needs to accept Valet's calls, usually its credential, as header name to value, such as Authorization to Bearer {{SNYK_TOKEN}}. Valet sends them on every call."
    • changedInput schema / properties / url / description
      Previous value: -"The endpoint's base URL, such as https://checks.example.com/snyk. Valet appends /v1/describe and the other Checker API paths to it."New value: +"Where the organization's checker service listens, such as https://checks.example.com/snyk. Valet calls /v1/describe and the other Checker API paths under it, so give the base, not a full path."
  3. Changed3 schema fields changed
    • changedInput schema / properties / checker / description
      Previous value: -"The name to save the checker under, such as snyk. A policy runs it as org:snyk, the org: prefix marking a checker the organization added. An existing name is replaced."New value: +"The checker's name, such as snyk. A policy runs it as org:snyk, the org: prefix marking a checker the organization added. Saving an existing name replaces that checker."
    • changedInput schema / properties / headers / description
      Previous value: -"Headers Valet sends on every call, as name to value. A credential header's value is one {{NAME}} reference to a secret env var of the organization, optionally after a scheme word, such as Bearer {{SNYK_TOKEN}}. Any other header's value is stored as written and refused if it looks like a credential."New value: +"Headers Valet sends on every call to the endpoint, as name to value, such as Authorization to Bearer {{SNYK_TOKEN}}."
    • changedInput schema / properties / url / description
      Previous value: -"The endpoint's base URL, such as https://checks.example.com/snyk. Valet appends /v1/describe and so on. Valet refuses an address that is not public."New value: +"The endpoint's base URL, such as https://checks.example.com/snyk. Valet appends /v1/describe and the other Checker API paths to it."
  4. Changed2 schema fields changed
    • changedInput schema / properties / checker / description
      Previous value: -"The checker's name, such as snyk. Policies name it org:snyk, and org:snyk is accepted here too. An existing name is replaced."New value: +"The name to save the checker under, such as snyk. A policy runs it as org:snyk, the org: prefix marking a checker the organization added. An existing name is replaced."
    • changedInput schema / properties / url / description
      Previous value: -"The endpoint's base URL, such as https://checks.example.com/snyk. Valet appends /v1/describe and so on. It is a public address with no user name or password, query, or fragment."New value: +"The endpoint's base URL, such as https://checks.example.com/snyk. Valet appends /v1/describe and so on. Valet refuses an address that is not public."
  5. Changed3 schema fields changed
    • changedInput schema / properties / headers / description
      Previous value: -"Headers Valet sends on every call, as name to value. A credential header's value is one {{NAME}} reference to a secret env var of the organization, optionally after a scheme word, such as Bearer {{SNYK_TOKEN}}."New value: +"Headers Valet sends on every call, as name to value. A credential header's value is one {{NAME}} reference to a secret env var of the organization, optionally after a scheme word, such as Bearer {{SNYK_TOKEN}}. Any other header's value is stored as written and refused if it looks like a credential."
    • changedInput schema / properties / url / description
      Previous value: -"The endpoint's base URL, such as https://checks.example.com/snyk. Valet appends /v1/describe and so on. It is a public address."New value: +"The endpoint's base URL, such as https://checks.example.com/snyk. Valet appends /v1/describe and so on. It is a public address with no user name or password, query, or fragment."
    • changedInput schema / properties / url / pattern
      Previous value: -"^https://[^?#]+$"New value: +"^https://[^/?#@]+(/[^?#]*)?$"
  6. Changed21 schema fields changed
    • changedInput schema / properties / checker / description
      Previous value: -"Required. The checker's name: lowercase letters, digits, and hyphens, such as snyk. Policies name it org:snyk, and org:snyk is accepted here too. An existing name is replaced."New value: +"The checker's name, such as snyk. Policies name it org:snyk, and org:snyk is accepted here too. An existing name is replaced."
    • addedInput schema / properties / checker / maxLength
      Added value: +67
    • addedInput schema / properties / checker / minLength
      Added value: +1
    • addedInput schema / properties / checker / pattern
      Added value: +"^(org:)?[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"
    • changedInput schema / properties / headers / description
      Previous value: -"Headers Valet sends on every call, as name to value. A credential's value must be a {{NAME}} reference to a secret env var of the organization, such as Bearer {{SNYK_TOKEN}}. Up to 16."New value: +"Headers Valet sends on every call, as name to value. A credential header's value is one {{NAME}} reference to a secret env var of the organization, optionally after a scheme word, such as Bearer {{SNYK_TOKEN}}."
    • addedInput schema / properties / headers / maxProperties
      Added value: +16
    • changedInput schema / properties / url / description
      Previous value: -"Required. The endpoint's base URL, https only, with no query or fragment, such as https://checks.example.com/snyk. Valet appends /v1/describe and so on. It must be a public address."New value: +"The endpoint's base URL, such as https://checks.example.com/snyk. Valet appends /v1/describe and so on. It is a public address."
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / url / pattern
      Added value: +"^https://[^?#]+$"
    • addedOutput schema / properties / checker / description
      Added value: +"The checker's name as a policy spells it, such as org:snyk. Pass it to set_policy as checker."
    • addedOutput schema / properties / description / description
      Added value: +"What the checker does, as the endpoint's describe operation reports it. Empty when the endpoint declares none."
    • addedOutput schema / properties / display_name / description
      Added value: +"The name a person reads, as the endpoint's describe operation reports it. Empty when the endpoint declares none."
    • addedOutput schema / properties / fields / description
      Added value: +"The settings a policy can give this checker, as the endpoint's describe operation reports them. Empty when it takes none."
    • addedOutput schema / properties / fields / items / properties / description / description
      Added value: +"What the setting is for. Empty when the checker gives none."
    • addedOutput schema / properties / fields / items / properties / name / description
      Added value: +"The setting's name, which set_policy takes as a key of settings."
    • addedOutput schema / properties / fields / items / properties / required / description
      Added value: +"True when a policy must give this setting."
    • addedOutput schema / properties / fields / items / properties / secret / description
      Added value: +"True when a person enters the value on a request page, not in settings."
    • addedOutput schema / properties / headers / description
      Added value: +"Headers Valet sends on every call, by name. A credential header shows its {{NAME}} reference, never a value. Empty when there are none."
    • addedOutput schema / properties / inputs / description
      Added value: +"The release files the endpoint asked for and this save approved: source, build, or both. Valet sends them to the URL for every release a policy naming this checker evaluates. Empty when it asked for none."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / url / description
      Added value: +"The endpoint's base URL as saved."
  7. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "checker": {
      +      "type": "string"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "display_name": {
      +      "type": "string"
      +    },
      +    "fields": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "description": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "required": {
      +            "type": "boolean"
      +          },
      +          "secret": {
      +            "type": "boolean"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "description",
      +          "required",
      +          "secret"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "headers": {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "inputs": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "null",
      +        "array"
      +      ]
      +    },
      +    "org": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "checker",
      +    "display_name",
      +    "description",
      +    "url",
      +    "headers",
      +    "inputs",
      +    "fields"
      +  ],
      +  "type": "object"
      +}
  8. Added

TDQS

A4.8/5.0
Behavior5/5

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

With annotations only saying destructive/openWorld/idempotent, the description adds the substance: Valet calls describe and saves nothing on failure, saving consents to sending release files (source, build, or both) to the endpoint, those files leave Valet's control, the approved file set is fixed, and an endpoint later asking for more becomes unavailable. It also discloses the Admin role requirement and the credential-header validation rules — far beyond what the annotations convey.

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?

Purpose, consent warning, header rules, and prerequisites are front-loaded in a logical order, and most sentences carry non-obvious information. There is some duplication with the schema — the org: prefix naming and the 'Authorization: Bearer {{SNYK_TOKEN}}' example are already defined in the checker and headers parameter descriptions.

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, open-world mutation with four parameters, nested headers, and a secret-handling surface, the description covers consent, validation failures, fixed approved-file sets, permissions, and even what the response names. An output schema exists, and the description appropriately only gestures at the returned file list rather than re-specifying it.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning on top: the exact {{NAME}} secret-reference rule, which header names count as credentials, what gets refused (raw secrets, credential-looking values in other headers, non-secret variable refs), and the `valet env set` workflow. It leaves url/org_name behavior mostly to the schema, which already handles it.

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 definition opens with a specific verb+resource ('Add an organization checker, or replace the one with the same name') and immediately defines what a checker is ('the organization's own HTTPS endpoint that implements Valet's Checker API'). It distinguishes the write from the read/inspect siblings by saying list_policies shows the organization's checkers and set_policy consumes the checker.

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?

It names the downstream consumer (set_policy running org:<name>), the discovery sibling (list_policies), the replacement semantics for an existing name, and a hard precondition — 'Confirm that with the user before you call this tool' — plus the prerequisite of setting the secret env var first. An agent knows both when to reach for it and what must happen before invoking it.

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