Skip to main content
Glama
Sign In

Thrifle

by com.thrifle
OverviewDiscussionsAdmin

Get a retailer's return policy

get_return_policy
Read-onlyIdempotent

Verified return policy for a US retailer: return window, free returns, restocking fee, holiday extension, non-returnable items, an A+–D− grade, how it compares with its category, and the retailer's own policy URL. Optionally pass what the shopper bought to surface a product-specific exception (e.g. electronics at Costco). Call this for any 'what is X's return policy' question.

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": {
      "merchant": "<merchant>"
    },
    "name": "get_return_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
productNoOptional: the product being returned, e.g. 'MacBook Air' or 'gift card', to check for a category exception
merchantYesRetailer name or thrifle.com slug, e.g. "Costco", "best-buy", "Nordstrom"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds behavioral insight beyond that: the data is 'Verified,' the optional product parameter surfaces 'a product-specific exception (e.g. electronics at Costco),' and the output includes category comparison. No contradictions with annotations.

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

Conciseness5/5

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

Two sentences with no filler. The first sentence front-loads the full list of returned fields; the second covers the optional parameter and the usage trigger. Every clause earns its place.

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?

Given only 2 parameters, complete schema coverage, and rich annotations, the description supplies everything needed to call correctly: what it returns, the optional product behavior, and when to use it. Since the return fields are enumerated, the absence of an output schema is not a gap.

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%, with both merchant and product already well described. The description mostly paraphrases the product parameter and gives a concrete example ('electronics at Costco'), but it doesn't add material meaning beyond the schema. Baseline 3 is appropriate.

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 opens with a specific resource, 'Verified return policy for a US retailer,' and enumerates exactly what is returned: return window, free returns, restocking fee, holiday extension, non-returnable items, grade, category comparison, and policy URL. The closing directive, 'Call this for any "what is X's return policy" question,' anchors a clear verb-resource pairing and differentiates it from search/compare siblings through its singular-retailer scope.

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?

The last sentence provides an explicit trigger: 'Call this for any "what is X's return policy" question.' However, it never names alternatives like search_return_policies or compare_return_policies, nor does it state when NOT to use this tool. Clear context but no exclusions, so it falls short of a perfect 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Thrifle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources