Skip to main content
Glama

Show a guide to selling a watch

selling_guide
Read-only

For someone thinking of selling a watch they own. Shows what similar watches are listed at today, next to what Watches in Stock has published about a quick sale to a dealer and about consignment. It makes no offer and works out no estimate, and it arranges no sale.

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": "selling_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoWhat comes with the watch.
dialNoOnly listings whose post names this dial colour, such as Black or Ice blue. Posts that do not name the dial are left out.
brandNoBrand name, such as Rolex or Patek Philippe.
queryNoWhat the customer asked for, in their words. Understands nicknames ("batgirl"), models ("daytona"), references ("126710BLNR"), years ("2016 or 2020") and budgets ("under 20k"), and budgets and dial colours in Spanish, French, German, Italian and Portuguese ("menos de 15 mil", "cadran bleu").
yearsNoSpecific production or card years.
referenceNoAn exact reference number, such as 126710BLNR or 5711/1A. The most exact search: pass it whenever the customer's words settle on one reference: a number they gave, in any spelling (5167R-001 and m126710blro-0001 are the 5167R and the 126710BLRO), a number with its metal ("5167 rose gold" is the 5167R), or one they picked from the references an answer offered. Nicknames go in query, which knows them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / reference / description
      Previous value: -"An exact reference number, such as 126710BLNR or 5711/1A. The most exact search: pass it whenever the customer's words settle on one reference: a number they gave, or one they picked from the references an answer offered. Nicknames go in query, which knows them."New value: +"An exact reference number, such as 126710BLNR or 5711/1A. The most exact search: pass it whenever the customer's words settle on one reference: a number they gave, in any spelling (5167R-001 and m126710blro-0001 are the 5167R and the 126710BLRO), a number with its metal (\"5167 rose gold\" is the 5167R), or one they picked from the references an answer offered. Nicknames go in query, which knows them."
  2. Changed1 schema field changed
    • changedInput schema / properties / reference / description
      Previous value: -"An exact reference number, such as 126710BLNR or 5711/1A."New value: +"An exact reference number, such as 126710BLNR or 5711/1A. The most exact search: pass it whenever the customer's words settle on one reference: a number they gave, or one they picked from the references an answer offered. Nicknames go in query, which knows them."
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"What the customer asked for, in their words. Understands nicknames (\"batgirl\"), models (\"daytona\"), references (\"126710BLNR\"), years (\"2016 or 2020\") and budgets (\"under 20k\")."New value: +"What the customer asked for, in their words. Understands nicknames (\"batgirl\"), models (\"daytona\"), references (\"126710BLNR\"), years (\"2016 or 2020\") and budgets (\"under 20k\"), and budgets and dial colours in Spanish, French, German, Italian and Portuguese (\"menos de 15 mil\", \"cadran bleu\")."
  4. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish read-only, non-destructive, open-world behavior. The description adds useful scope beyond that: it shows today's similar listings and published dealer/consignment information, and explicitly performs no offer, no estimate, and no sale arrangement. It does not discuss data freshness or authentication, but the added behavioral boundaries are meaningful.

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?

The description is short and front-loads the audience before describing outputs and boundaries. Every sentence serves a purpose, though the final clause is slightly repetitive with "makes no offer" and "arranges no sale." It remains clear and easy to parse.

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 read-only guide with six optional filters and no output schema, the description covers the audience, the information shown, and important behavioral limits. It reasonably leaves filter semantics to the rich schema, though it could clarify whether the guide presents static guidance or live listing excerpts.

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 detailed documentation for all six optional filters, including enum values and query-language behavior. The description adds no additional parameter meaning, which is acceptable when the schema carries that burden. Baseline 3 applies.

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 gives a specific resource and scope: a guide for someone thinking of selling a watch, showing similar listings alongside published information on dealer quick sales and consignment. It clearly differentiates itself from transactional tools by stating it makes no offer, estimate, or sale. It does not explicitly contrast itself with siblings such as price_check or market_report, so it stops short of 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 Guidelines3/5

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

"For someone thinking of selling a watch they own" establishes a clear use case, and the exclusions clarify that it is not for making offers or estimates. However, it does not name alternatives or say when another sibling tool would be more appropriate. Guidance is implied rather than explicit.

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