Skip to main content
Glama

alpha-sentinel-mcp

tokenized_stock_nav_deviation

Compare Chainlink NAV/reference to underlying equity spot (research spread).

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

Cost: $0.02 USD per call

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "tokenized_stock_nav_deviation"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add genuinely useful operational context: a per-call cost of $0.02 USD and a jurisdiction restriction (Coinbase tokenized stocks not offered to U.S. persons). It says nothing about output shape, data latency/freshness of the NAV reference, or behavior on an unrecognized symbol, which matters for a priced research call.

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?

The core comparison is front-loaded in the first sentence, and the cost line is a compact, high-value trailing fact. The legal boilerplate is somewhat prominent relative to the functional content, but it is short and does not obscure the purpose.

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 and no annotations, the description should explain what the returned spread looks like (a percentage, an absolute gap, direction) and how the symbol is keyed. Cost and jurisdiction are covered, but those two gaps leave the agent under-informed for a one-parameter, priced research call.

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?

There is one required parameter, 'symbol', and schema description coverage is 0%, so the description is the only place meaning could be added — and it never mentions the parameter. An agent cannot tell whether 'symbol' expects an equity ticker (e.g. AAPL), a token symbol, or a Chainlink feed identifier, which is a real ambiguity for a comparison between two price sources.

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 comparison: Chainlink NAV/reference versus underlying equity spot, framed as a research spread. That is a concrete verb-plus-resource statement an agent can act on. It does not, however, distinguish itself from the sibling tokenized_stock_peg_gap_radar, which on its name alone sounds like a near-identical spread computation, so the agent gets no help choosing between them.

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?

There is a scope boundary ('RESEARCH ONLY', 'no trading, execution, custody, or swaps'), which tells the agent what the tool is not for, but no positive guidance on when to call it instead of peg_gap_radar or the other tokenized-stock research tools. No prerequisites, no data-freshness conditions, no alternatives are named.

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.