Skip to main content
Glama

Pricemend return policies

statutory_rights

What the law in a country gives a shopper on top of whatever the retailer offers, with the legislation cited. Covers US, CA, GB, ES, AE, SA, EG and IN. Worth checking outside the US, where the statutory right is often stronger than the shop's own policy.

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": {
      "country": "<country>"
    },
    "name": "statutory_rights"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 behavioral burden. It usefully discloses that results cite legislation and enumerates the eight supported countries, but it never says what happens for an unsupported country, whether the response is a fixed record or free text, or how coverage gaps are signaled.

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?

Roughly two short sentences: what it returns, then where it applies. Coverage and the when-to-use cue are front-loaded with no padding, though the opening sentence is a verbless fragment that takes a beat to parse.

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 one-parameter informational lookup with no annotations and no output schema, the definition covers what the tool returns, the country set, and when it is worth calling. The only material gap is unsupported-country behavior, which an agent would want to know before invoking.

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 0% — the single `country` parameter is an undescribed string — so the description must compensate, and it does by listing the supported values (US, CA, GB, ES, AE, SA, EG, IN). It stops short of stating explicitly that only those codes are accepted, so the parameter contract is implied rather than declared.

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 states a specific resource — the statutory rights the law grants a shopper in a given country, with the governing legislation cited — and implicitly separates it from retailer-provided terms ('on top of whatever the retailer offers'), which distinguishes it from siblings like store_policy and return_deadline. It lacks a clean verb (it reads as a noun phrase), so it is clear but not maximally crisp.

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 gives a concrete usage cue: check this when shopping outside the US, because statutory rights there are often stronger than store policy. That frames the when-to-use case and the complementarity with retailer-policy tools, but it offers no explicit exclusions or named alternatives for the US case.

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