Skip to main content
Glama

Pricemend return policies

find_store

Find a retailer in Pricemend's coverage from a name a person used, such as 'old navy' or 'btech'. Returns store ids to pass to the other tools. Start here when you have a shop's name but not its id.

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": {
      "query": "<query>"
    },
    "name": "find_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
countryNo

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?

No annotations are supplied, so the description carries the full behavioral burden. It discloses the lookup is name-based and informal ("old navy", "btech") and that the return value is store ids, which usefully implies a read-only resolution step, but it says nothing about what happens on no match, ambiguous multi-match results, or whether multiple candidates can come back.

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?

Three short sentences with no filler: what it does, what it returns, and when to reach for it, in that order. Every sentence carries distinct information and the usage cue is front-loaded.

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 two-parameter lookup with no output schema and no annotations, the description covers purpose, return, and entry-point role adequately. It leaves gaps on the country filter's effect and on result-cardinality behavior, which matter for correctly chaining into the other tools.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must supply parameter meaning. The two examples do add real signal about the query parameter (informal, abbreviated, case-insensitive name forms), but the country parameter is never mentioned at all and neither parameter's format or filtering behavior is explained.

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?

States a specific verb and resource ("Find a retailer in Pricemend's coverage") and names the input shape ("a name a person used") and the output ("store ids"). It also distinguishes itself from siblings by framing itself as the entry point ("Start here when you have a shop's name but not its id"), so an agent can tell it apart from coverage or store_policy without opening a schema.

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?

Gives an explicit trigger condition: use this when you have a shop's name but not its id, and notes the result feeds "the other tools." There is no explicit when-not or named alternative for the case where an id is already known, which keeps it short of a 5.

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