Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

tokenized_stock_peg_gap_radar

Read-onlyIdempotent

Monitor tokenized stock DEX prices against underlying references and flag gaps that exceed a configurable percentage threshold.

Instructions

Peg-Gap Radar: onchain DEX price vs underlying reference, alerts over threshold %.

RESEARCH ONLY — not investment advice. No trading, execution, custody, or swaps. Coinbase tokenized stocks are not offered to U.S. persons.

Cost: $0.03 USD per call

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

Input Schema

NameRequiredDescriptionDefault
symbolsNo
page_sizeNo
alert_threshold_pctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, idempotent, and open-world, so safety is covered. The description adds genuinely non-obvious context beyond that: a $0.03 per-call cost, an explicit research-only scope with no execution or custody, and a U.S.-persons eligibility restriction. It still leaves the mechanics of 'alerts' unspecified (returned as flagged rows vs. pushed notifications).

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

Conciseness5/5

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

The purpose is front-loaded in the first sentence, and the remaining lines are compliance and pricing facts that each carry operational weight for an agent deciding whether to call. No filler or restatement of the tool name.

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 three optional params, no output schema, and no required inputs, the description omits what a result row actually contains (gap percent, reference source, timestamp) and how alerting is delivered, which an agent needs to interpret or relay results. Compliance and cost are covered well, but the data-shape gap is real.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry all three parameters. It only indirectly explains alert_threshold_pct via 'alerts over threshold %', and says nothing about the symbols array format (ticker casing, whether omission means all stocks) or page_size for pagination.

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 a specific computation: onchain DEX price compared against an underlying reference, with alerts surfaced when the deviation exceeds a threshold percentage. That is a concrete verb-plus-resource statement an agent can match to a user request about peg/depeg monitoring. It does not distinguish itself from a close sibling such as tokenized_stock_nav_deviation, 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?

Usage is only implied: the threshold framing suggests scanning tokenized stocks for price divergence, and the disclaimer rules out trading asks. There is no explicit statement of when to pick this over nav_deviation or fetch_price, and no guidance on how to choose a threshold or whether omitting symbols scans everything.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.