Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

tokenized_stock_research_brief

Read-onlyIdempotent

Generate a multi-symbol research brief for tokenized stocks, combining metadata, NAV staleness checks, and deviation notes for analysis.

Instructions

Multi-symbol research brief: metadata, NAV staleness, deviation notes.

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

Cost: $0.05 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": {
      "symbols": "<symbols>"
    },
    "name": "tokenized_stock_research_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint='false', so the safety profile is covered. The description adds genuinely new operational context: a $0.05 USD per-call cost and a jurisdictional restriction (not offered to U.S. persons), which matter for invocation decisions. It does not disclose rate limits, latency, or error behavior on invalid symbols.

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 payload (what the brief contains) is front-loaded ahead of the disclaimers, and the cost line is set off clearly. The legal/restriction block is longer than the functional description, which slightly dilutes signal for an agent scanning for capability.

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?

For a one-parameter read tool with no output schema, the description covers contents, cost, and access constraints reasonably well. What is missing is the shape of the response (per-symbol sections? staleness units? deviation thresholds) and behavior on partial or unrecognized symbols.

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?

Schema description coverage is 0% for the single 'symbols' array parameter, so the description must carry the burden. It does add meaning by labeling the operation 'multi-symbol', confirming a batch of identifiers, though it never clarifies symbol format (ticker vs. asset ID, case sensitivity) or what happens at the maxItems=10 boundary.

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 concrete deliverable ('Multi-symbol research brief') and enumerates its contents (metadata, NAV staleness, deviation notes), which is far more specific than the tool name alone. It does not explicitly contrast itself with narrower siblings like tokenized_stock_nav_deviation or tokenized_stock_lookup, leaving the boundary to be inferred from the 'multi-symbol' scope.

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?

The only usage framing is the 'RESEARCH ONLY' disclaimer, which constrains purpose (no trading, execution, custody, swaps) rather than tool selection. It never says when to call this instead of the single-purpose siblings such as nav_deviation or lookup, so an agent must guess at the multi-symbol aggregate use case.

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