Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_store_get_settings

Read-onlyIdempotent

Retrieve store settings for a location using its altId and altType with a sub-account token, enabling inspection of store configuration for updates or troubleshooting.

Instructions

Get Store Settings Get store settings by altId and altType. Endpoint: GET /store/store-setting (Version header: v3; source: v3/store-v3.json) Requires a Sub-Account (location) token.

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": {
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_store_get_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
altTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add other context — and it does, by disclosing the auth prerequisite (Sub-Account/location token) and the endpoint plus v3 version header. It adds nothing about response shape or failure modes, so not a 5.

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?

Four short lines, front-loaded with the action and key inputs, with the auth constraint coming before the API metadata. Minor waste: the second line repeats the title and the endpoint line is developer metadata rather than agent guidance.

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 simple two-parameter read with no output schema and full annotation coverage, the essentials for calling it are present (resource, keys, token requirement). However, it never indicates what 'store settings' actually contains, and with no output schema the agent has no other source for that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: altId is documented ('Location Id or Agency Id') while altType has an enum but no description. The description says only 'by altId and altType' and never explains that altType is restricted to 'location' or what altId resolves to, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Get store settings') and names the two required keys, which clearly separates it from the store mutation siblings such as ghl_store_upsert_settings. The second line largely restates the title plus parameter names rather than adding scope detail, so it stops short of a 5.

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 name and the 'Requires a Sub-Account (location) token' prerequisite. It never says when to call this versus ghl_store_upsert_settings or the shipping-zone/rate getters, and gives no exclusions.

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