Skip to main content
Glama

woo_helper_get_settings

Retrieve Woo helper settings for a specified site, with secret values shown only as { set } to prevent raw credential exposure.

Instructions

cvrt-woo-helper settings (secrets as { set }, never raw).

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_get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.9/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 behavioral burden, and it does disclose one genuinely useful trait: secrets come back as "{ set }" placeholders and are never exposed raw. That is real value beyond structured fields, but it says nothing about read-only semantics, permissions, error behavior, or what other setting keys are returned.

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?

It is one short fragment with zero padding, and the important behavioral caveat about masked secrets is front-loaded. The telegraphed "cvrt" abbreviation costs a little legibility but keeps it efficient.

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?

This is a simple one-parameter read with no output schema, so the description should carry the return-shape load; it covers the secret-masking rule but not what settings categories or keys are present in the response. Adequate, but an agent still has to call it to learn the payload.

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 coverage is 100% for the single required "site" parameter, which already documents "Site id (see list_sites)". The description adds no syntax, format, or defaulting detail for that parameter, so the baseline 3 applies.

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

Purpose3/5

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

The phrase "cvrt-woo-helper settings" names the resource and the namespace, which does help separate it from siblings like seo_get_settings, wp_get_settings, and stripe_get_settings. But it never states a verb such as "returns" or "retrieves" — the reading direction comes only from the tool name — so it borders on restating the name.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus woo_helper_update_settings or the other get_settings siblings, and no prerequisite/auth context. The agent must infer read-vs-write from the tool name alone.

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