Skip to main content
Glama

Pricemend return policies

store_policy

A retailer's return and price-adjustment rules: how many days, whether it refunds a price drop or only takes returns, what's excluded, and whether Pricemend can read its live prices. Use find_store first if you only have a name.

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": {
      "store": "<store>"
    },
    "name": "store_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 implicitly frames this as a read-only policy lookup and usefully discloses that one of the returned facts is whether Pricemend can access the retailer's live prices, which signals possible capability gaps per store. It does not cover failure behavior for an unknown store or what the result looks like structurally.

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?

Two sentences, front-loaded with the substantive content and ending with the actionable prerequisite. The enumerated clause list is dense but every item conveys a distinct return field, so little is wasted.

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 lookup with no output schema and no annotations, the description covers what information comes back and how to source the identifier. The remaining gap is the format of the `store` value and not-found behavior, both of which an agent would otherwise have to discover by trial.

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?

The single `store` parameter has 0% schema description coverage, so the description must compensate. The find_store hint implies the argument should be a resolved store identifier rather than a raw name, which is real added meaning, but it never defines the accepted format or whether a name would also work.

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 names the resource precisely (a retailer's return and price-adjustment rules) and enumerates the specific facts returned: return window in days, price-drop refund vs. return-only, exclusions, and whether live prices are readable. That enumeration distinguishes it from siblings like return_deadline and check_price. The retrieval verb itself is only implied by the noun phrase, which keeps it from 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 Guidelines4/5

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

It gives an explicit prerequisite: 'Use find_store first if you only have a name,' which tells the agent how to obtain the required `store` argument. It does not state when to prefer this over return_deadline or statutory_rights, so overlap with those siblings is left to inference.

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