Skip to main content
Glama

Pricemend return policies

coverage

What Pricemend covers: how many retailers in which countries, how many have live price checking, and how the policy records are sourced. Call this when asked what you can and can't answer about returns.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose what the payload contains (counts of retailers and countries, live price-checking status, sourcing of policy records), which substitutes usefully for the absent output schema. It says nothing about whether the data is static or refreshed, whether calling it has any side effects, or how large the response is, so behavior is only partially covered.

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, no filler, with the content of the response front-loaded and the trigger placed second. Every clause earns its place and nothing is repeated from the schema.

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 zero-parameter, annotation-free tool with no output schema, the description adequately characterizes what comes back and when to call it. The remaining gap is freshness/format of the coverage data, which an agent might want before relying on the numbers.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly spends no words on arguments.

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 a specific resource (service coverage) and enumerates its dimensions: retailer count, country spread, live price-checking coverage, and policy sourcing. That is enough to separate it from the transactional siblings (check_price, find_store, return_deadline), though it never says explicitly that this is a metadata/introspection tool as opposed to a lookup.

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 trigger: 'Call this when asked what you can and can't answer about returns.' That is a clear usage condition rather than an implied one. It stops short of naming alternatives or exclusions, and the trigger ('about returns') is narrower than the coverage dimensions listed, leaving mild ambiguity about whether it should also be called for pricing or store-location scope questions.

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