Skip to main content
Glama

Listing check-up

listing_checkup
Read-onlyIdempotent

A live health check of your active marketplace listings, read from the marketplace (cached up to 5 minutes): each listing's price (in its own currency) against the SlabLineage price (USD), percentVsSl (whole percent above + or below -, null when it can't be compared), priceVsSl (priced_high, in_range, under_sl or no_sl_price), watchers, bids, days live and attentionReasons (priced_high: more than 10% over; no_watchers: none after 7+ days). Listings not matched to a SlabLineage card have no SL price. Different from my_listings, which reads SlabLineage's own records with no live call. Needs-attention listings at the top, up to 50; the summary counts them all.

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

Input Schema

NameRequiredDescriptionDefault
onlyNeedsAttentionNoReturn just the listings that need attention (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses caching (up to 5 minutes stale), currency handling (per-listing currency vs USD baseline), null semantics for incomparable listings, unmatched-card behavior, and output ordering and cap. This is exactly the operational context annotations cannot convey.

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?

Purpose and scope are front-loaded, and the parenthetical enum definitions are efficient rather than redundant. It is a single dense sentence, though, so the operational facts (cache window, 50-item cap, summary counts) are buried mid-string rather than set apart.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden of describing return values, and it does: per-listing fields, the percentVsSl and priceVsSl semantics, the attentionReasons enum, sort order, item cap, and the summary's counting behavior. Nothing material is left for the agent to guess.

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?

Schema coverage is 100% for the single boolean parameter, so the schema already carries the baseline. The description still adds real meaning by defining what 'needs attention' means (priced_high over 10%, no_watchers after 7+ days) and noting needs-attention listings sort to the top, up to 50.

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?

The description opens with a specific verb and resource ('live health check of your active marketplace listings, read from the marketplace') and immediately distinguishes itself from my_listings, which it says reads SlabLineage's own records with no live call. An agent can tell which tool to pick without opening either schema.

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

Usage Guidelines5/5

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

The alternative is named explicitly ('Different from my_listings... with no live call'), giving the discriminating condition: live marketplace data versus internal records. The onlyNeedsAttention behavior is also spelled out, so the agent knows the filtered mode exists.

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