Skip to main content
Glama

legal_get_shop_withdrawal

Retrieves WooCommerce withdrawal function settings, including labels, emails, footer link, account menu, order actions, and withdrawal period for compliance review.

Instructions

Withdrawal function settings (Widerrufsbutton, § 356a BGB / § 13a FAGG) of cvrt-legal 0.12.1+ on a WooCommerce shop: whether WooCommerce's own withdrawal feature is on, the prescribed labels, single email, item picker, footer link, My Account menu, order actions, which emails carry the link, withdrawal period. 404 when WooCommerce is not active.

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": "legal_get_shop_withdrawal"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.6/5.0
Behavior4/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 does disclose a concrete failure mode: a 404 when WooCommerce is not active. It also effectively describes the return payload by enumerating the settings returned, substituting for the missing output schema. It stops short of stating auth/permission requirements, though read-only behavior is implied by the get naming and settings framing.

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?

One dense sentence, front-loaded with the resource and scope, with each clause naming a concrete returned setting rather than padding. The embedded legal citations (§ 356a BGB / § 13a FAGG) and version string add precision but make the sentence slightly heavy; still, no filler sentences.

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?

Given a one-parameter read tool with no output schema, the description gives enough to know what comes back and one error condition. However, it omits pagination/response shape details and any permission or multi-site caveats, leaving a few gaps for an agent to discover at runtime.

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?

There is a single parameter (site) with 100% schema description coverage, so the schema already explains it ("Site id (see list_sites)"). The description adds no further meaning about the site parameter, which matches the baseline-3 rule for high schema coverage.

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 resource – the withdrawal (Widerrufsbutton) settings of the cvrt-legal plugin on a WooCommerce shop – and enumerates the concrete settings it covers (WooCommerce feature toggle, labels, emails, footer link, My Account menu, order actions, withdrawal period). An agent can distinguish it from the write counterpart legal_put_shop_withdrawal by the "settings ... whether ... is on" framing, though no sibling is named explicitly.

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: the enumerative "settings of a WooCommerce shop" phrasing tells an agent this is the read path for withdrawal configuration, and the 404-when-WooCommerce-inactive note signals a precondition. There is no explicit when-to-use/when-not guidance and no mention of legal_put_shop_withdrawal as the alternative for changing these values.

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