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

ghl-mcp-server-v2

by zackscriven

ghl_store_get_shipping_rate

Read-onlyIdempotent

Retrieves a specific shipping rate from a store shipping zone using the shipping zone ID and shipping rate ID to verify costs or configure fulfillment.

Instructions

Get Shipping Rate The "List Shipping Rate" API allows to retrieve a paginated list of shipping rate. Endpoint: GET /store/shipping-zone/{shippingZoneId}/shipping-rate/{shippingRateId} (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": {
      "shippingZoneId": "<shippingZoneId>",
      "shippingRateId": "<shippingRateId>",
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_store_get_shipping_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id or Agency Id
altTypeYes
shippingRateIdYesID of the shipping rate that needs to be returned
shippingZoneIdYesID of the shipping zone

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add genuinely useful non-schema context — the auth requirement ("Requires a Sub-Account (location) token") and API version header — but the "paginated list" claim is misleading for a single-record fetch and no pagination parameters exist in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The tool's actual intent is front-loaded in the first line, but the following sentences are partly boilerplate ("source: v3/store-v3.json") and partly counterproductive ("List ... paginated list"). Trimming the internal artifact reference and fixing the list wording would make every sentence earn its place.

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 single-record read with full annotation coverage and 75% schema description coverage, little is strictly missing. However, the description never resolves the confusion with list_shipping_rates and get_available_shipping_rates, and its "paginated list" phrasing could lead an agent to expect a paginated response that this endpoint does not return.

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

Parameters4/5

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

Schema coverage is 75% and each parameter carries a description, so the schema does most of the work. The description contributes extra meaning by showing shippingZoneId and shippingRateId as path parameters in the endpoint template, clarifying their role, though altId/altType receive no mention.

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 tool name and first line say "Get Shipping Rate", but the body immediately describes it as the "List Shipping Rate" API returning a "paginated list", even though the endpoint is a single-resource GET with shippingRateId in the path. An agent can infer it fetches one rate, but the wording blurs it with the sibling ghl_store_list_shipping_rates, so purpose is only partially disambiguated.

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?

No statement of when to use this versus ghl_store_list_shipping_rates or ghl_store_get_available_shipping_rates. The only implicit guidance is the endpoint path, which hints that both a zone ID and a rate ID are required, but that is inference rather than guidance.

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