Skip to main content
Glama

get_settings

Read-only

Read the site's settings (key scope settings:read): per form where notifications go (staff_mail, whether Slack is set — the URL is masked and never returned), the auto-reply text, GTM, the GA4 measurement id and Search Console's verification token (effective.ga4_measurement_id is what the delivery actually injects: null while a GTM container is set, because two tags would count every lead twice), the embedded form's bot check (form_turnstile: required / off) and the site's language (site_locale; null = from the schema). Changing them is not possible with this tool.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite ID (the id from list_sites, e.g. "my-shop")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the required scope (settings:read), that the Slack URL is masked and never returned, why effective.ga4_measurement_id can be null when GTM is active, and that null site_locale means the schema default. This is substantial behavioral context for a read-only tool.

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?

The key purpose is front-loaded in "Read the site's settings," and the details that follow are useful return-value disclosures. However, the description is a single dense sentence with nested parentheticals, making it harder to scan than it could be.

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?

With no output schema, the description carries the burden of explaining return values, and it does so comprehensively: notifications, auto-reply, GTM, GA4, Search Console, bot check, and locale. It also covers auth scope and non-mutability, leaving no critical gap for correct invocation.

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 description coverage is 100%, and the single site parameter is already documented in the schema as the ID from list_sites. The description adds useful context about the site being the subject of the read but does not add syntax or selection guidance beyond the schema.

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 description gives a specific verb and resource ("Read the site's settings") and enumerates the settings returned, so the agent knows exactly what the tool exposes. It also distinguishes itself from the mutation sibling by stating that changing settings is not possible with this tool.

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

Usage Guidelines4/5

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

It clearly signals when this tool applies (reading settings for a site) and when it does not (changing them), which implies update_settings is the alternative. It does not explicitly name that alternative or explain edge cases where a more specialized getter such as get_form_turnstile might be preferred.

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