Skip to main content
Glama

woo_helper_update_settings

Update cvrt-woo-helper settings for a site: store a write-only GitHub token for plugin updates, or clear the saved token when needed.

Instructions

Update cvrt-woo-helper settings. github_token is write-only (blank or omitted keeps the stored one); clear_github_token:true deletes it.

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": {
      "site": "<site>"
    },
    "name": "woo_helper_update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
github_tokenNoGitHub token for plugin updates (write-only)
clear_github_tokenNoDelete the stored GitHub token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: the token is write-only, a blank/omitted value preserves the stored one, and clear_github_token:true destroys it. That is valuable, but it omits whether the call is reversible, what permissions are required, and whether unspecified settings are reset or preserved.

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?

Two sentences, front-loaded with the action and followed immediately by the one non-obvious parameter rule. Every clause earns its place and there is no filler.

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

Completeness3/5

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

For a 3-parameter mutation tool with no annotations and no output schema, the definition covers the risky token semantics but leaves open what the response looks like, whether the update is partial or full, and what 'settings' beyond the token exist. Adequate minimum, not complete.

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 would be 3, but the description genuinely adds semantics the schema does not: that omitting or blanking github_token keeps the existing value rather than nulling it. The only gap is 'site', which is left entirely to the schema's list_sites pointer.

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?

The description names a specific verb and resource ('Update cvrt-woo-helper settings'), which is enough to distinguish it from the read counterpart woo_helper_get_settings by name alone. It stops short of explicitly routing against the other update_* siblings (update_emails, update_stripe), so it is clear but not fully differentiated.

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?

Usage is only implied by the semantics: the write-only note and the 'clear_github_token:true deletes it' clause tell an agent how to manipulate the token, but there is no explicit when-to-use versus alternatives statement or prerequisite (e.g. permissions, whether other settings are left untouched). An agent can infer it is the settings-mutation tool, but must guess the rest.

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

Deploy Server

Other Tools