Skip to main content
Glama

Alert marketplace

get_marketplace_alerts
Read-only

Alert templates sold by OwlChart members: bundles of alert types (price, open interest, liquidity magnet, funding, ETF verdict, stablecoin mint, large transfer, regulatory keyword) with coins and thresholds, at a monthly price. With a template pass (Bearer owlpass_ from /api/products/alert_marketplace/buy?for=ID) and the template id, returns the full bundle of alert settings.

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

Input Schema

NameRequiredDescriptionDefault
templateNoA template id you hold a pass for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully adds the Bearer owlpass_ authorization requirement and points at the purchase endpoint, but says nothing about pass expiry, failure modes when the pass is missing or invalid, or whether bundle contents can change.

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?

Two sentences, purpose front-loaded, no filler. The second sentence is dense with a nested parenthetical containing a URL and query string, which costs a little readability but carries real information.

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?

No output schema exists, but the description does state the return value at a useful level ('full bundle of alert settings'), and it covers auth and acquisition of the required pass. Only error/permission-failure behavior is missing for a caller gating on a credential.

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% and the single parameter is already documented, so the baseline is 3. The description adds mild value by explaining where the pass behind that id comes from, but nothing about id format or behavior for unknown ids.

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 precisely (member-sold alert templates: bundles of alert types with coins and thresholds, priced monthly) and the outcome (returns the full bundle of alert settings). It implicitly distinguishes itself from user-facing alert tools like check_alerts/create_alert, but never states the distinction, and the no-parameter/listing behavior is left unstated.

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

Usage Guidelines2/5

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

It gives a prerequisite (a template pass plus template id) but no guidance on when to call this versus check_alerts, list_alerts, or create_alert, and no explanation of what happens when called with no template argument. The agent must infer the marketplace-browsing case entirely.

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