Skip to main content
Glama

Pricemend return policies

return_deadline

The last day a shopper can act on something they bought, and what to do when they get there. This is the main tool: give it the store and the purchase date and it returns the deadline, the days left, and whether the shop refunds the difference or the shopper should return and rebuy. channel is 'online' or 'in_store'.

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>",
      "purchased": "<purchased>"
    },
    "name": "return_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYes
memberNo
channelNoonline
purchasedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the computed outputs (deadline, days left, refund-difference vs return-and-rebuy recommendation). It does not state that this is a read-only calculation, how it handles unknown stores or malformed dates, or whether member status changes the result. Some behavioral context is present but the mutation/error edge cases are unaddressed — though the tool is clearly a passive lookup by construction.

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

Conciseness3/5

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

The opening sentence is narrative and slightly indirect, spending words on 'something they bought' before getting to the actual resource. The core content is dense and largely front-loaded, with the return values and channel values spelled out efficiently. Minor tightening (leading with the deadline computation, dropping the 'what to do when they get there' flourish) would sharpen it.

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 four-parameter, no-annotation, no-output-schema tool, the description covers the return payload well, which is important since there is no output schema. Gaps remain: the 'member' flag is unexplained and the date format for 'purchased' is unspecified. It is close to sufficient to call correctly but not complete.

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 0%, so the description has to compensate, and it partially does: it explains 'store' and 'purchased' as the two required inputs, and it gives the allowed values for 'channel' ('online' or 'in_store') that the schema itself does not enumerate. However, the 'member' boolean parameter is never mentioned, so one of four parameters remains entirely undefined. It also gives no format hint for the purchase date string.

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 uses a clear verb+resource framing: give the store and purchase date, and it returns the return deadline, days left, and refund-vs-rebuy guidance. It also signals primacy with 'This is the main tool', though it doesn't name a specific sibling it displaces. The first sentence is a bit indirect ('the last day a shopper can act on something they bought') but the follow-up makes the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: 'This is the main tool' and 'give it the store and the purchase date' suggest it is the default entry point. There is no explicit when-not guidance and no alternative tool (e.g., store_policy, statutory_rights) is named as a fallback. Adequate but leaves routing decisions 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