Skip to main content
Glama

alpha-sentinel-mcp

tokenized_stock_peg_gap_radar

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 observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that no trading, execution, custody, or swaps occur, adds a jurisdictional restriction (not offered to U.S. persons), and states a concrete cost of $0.03 per call. What it omits is return shape, data freshness/latency of the DEX vs reference prices, and pagination behavior.

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?

Front-loaded with the core mechanism in one line, then legal and cost caveats in short, clearly separated blocks. The disclaimer paragraph is slightly longer than strictly needed, but nothing is buried or wasted.

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?

For a zero-required-parameter tool with no output schema, the description covers the non-obvious behavioral risks (cost, legal scope, non-execution) well. However, an agent still cannot tell what the response contains (alert records vs a list of gaps) or how page_size affects results, which matters given the absence of an output schema.

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 explain all three parameters. It only alludes to one ('threshold %', mapping to alert_threshold_pct) and says nothing about what symbols accepts or what page_size controls, leaving two parameters entirely undocumented.

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 first line gives a specific comparison ('onchain DEX price vs underlying reference') and the output concept ('alerts over threshold %'), which is far more than a restatement of the name. It does not explicitly distinguish itself from the similarly-scoped sibling tokenized_stock_nav_deviation, so it falls 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 mention of alert thresholds suggests a monitoring/detection use case, and the 'RESEARCH ONLY' banner implies it is not for execution. There is no explicit statement of when to call this versus the sibling deviation or research tools, and no exclusions or prerequisites beyond the legal note.

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.