Skip to main content
Glama

My price alerts

my_price_alerts
Read-onlyIdempotent

Your SlabLineage price alerts: the card, grading company and grade, your maximum price in USD, liveMatches (live marketplace listings at or under that price right now) and the card page. No listing details.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered upstream. The description adds useful scope detail by clarifying that liveMatches are live marketplace listings at or under the max price right now, and it explicitly excludes listing details — but it says nothing about empty results, ordering, or how many alerts 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.

Conciseness4/5

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

A single dense sentence that front-loads the resource and then lists the returned fields with a parenthetical defining liveMatches. Nothing is redundant, though 'the card page' is an under-explained field name and the run-on structure is slightly hard to parse at a glance.

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?

With no output schema, the description carries the burden of explaining returns, and it does enumerate the fields including liveMatches. However, key behaviors remain unstated: what an empty alert list looks like, whether liveMatches can be empty within an existing alert, and whether the card page is a URL or an identifier.

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 nothing for the description to disambiguate at the input layer; the baseline of 4 applies. No parameter claims in the description conflict with the empty schema.

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 the resource (SlabLineage price alerts) and enumerates what each alert contains: card, grading company and grade, max price in USD, liveMatches, and card page. That is specific enough to distinguish it from siblings like my_listings or my_collection_summary, though it describes the payload rather than stating a clean verb like 'retrieve your configured price alerts'.

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: the possessive framing plus 'No listing details' signals this is the user's own alert records and is not a listing-detail lookup. No sibling or alternative is named for when listing details actually are needed (e.g., my_listings), and no condition such as 'no alerts configured' is discussed.

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