Skip to main content
Glama

stripe_get_settings

Retrieve WooCommerce Stripe Gateway settings with secrets masked, plus the active live or test mode, for a given site.

Instructions

WooCommerce Stripe Gateway settings, secrets masked, plus the active mode (live/test).

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/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 does disclose two meaningful behaviors: secrets are masked in the response, and the active mode (live/test) is included. It omits whether the operation is strictly read-only, what permissions are needed, and what happens on an invalid site id.

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?

A single tight fragment that front-loads the resource and then the two notable output traits. Efficient, though the fragmentary grammar makes it slightly less scannable than a complete clause would be.

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

Completeness4/5

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

For a simple single-parameter read tool with no output schema, the description covers resource identity, response characteristics (masked secrets, mode), and is adequate to call correctly. Minor gaps around permissions and failure behavior keep it from a 5.

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?

Only one parameter (site), and the schema already documents it at 100% coverage including a pointer to list_sites. The description adds no format or example detail beyond the schema, so the baseline 3 applies.

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?

Names the specific resource (WooCommerce Stripe Gateway settings) and what the response contains (secrets masked, active mode). An agent can distinguish it from stripe_list_charges or woo_helper_get_settings, though it never explicitly names a sibling to differentiate against.

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 when-to-use or when-not-to-use guidance, and no pointer to alternatives such as stripe_get_account or stripe_list_payment_method_configs for related data. The agent must infer usage purely from the resource name.

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