Skip to main content
Glama

alpha-sentinel-mcp

tokenized_stock_research_brief

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 observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose genuinely non-obvious behavior: a per-call cost of $0.05 USD and an eligibility restriction that tokenized stocks are not offered to U.S. persons. Those are real operational constraints an agent must know before calling. What is missing is the return shape beyond the three named sections and any rate-limit or latency 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?

The purpose statement is front-loaded in a single line, followed by a compact disclosure block and a one-line cost note. Little waste, though the legal disclaimer occupies a larger share of the text than the functional description does.

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?

No output schema and no annotations mean the description must cover everything, and it does name the three output sections plus cost and eligibility. It still leaves the agent without symbol-format guidance and without any statement of what a 'deviation note' contains, so a caller could plausibly mis-format inputs.

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?

There is one parameter (symbols array) with 0% schema description coverage, so the description has to compensate. 'Multi-symbol' confirms the array is intended to hold several identifiers, but it never states the expected symbol format (bare ticker vs. exchange-qualified) nor mentions the 10-item cap. Marginal value added over the schema.

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?

Names a concrete deliverable (a multi-symbol research brief) and enumerates its contents: metadata, NAV staleness, deviation notes. That distinguishes it reasonably well from single-purpose siblings like tokenized_stock_nav_deviation or tokenized_stock_lookup, though the action verb is implicit ('research brief') rather than stated.

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?

The 'RESEARCH ONLY — not investment advice. No trading, execution, custody, or swaps' block does establish a when-not-to-use boundary against execution-oriented workflows. However, it never says when to pick this over the closely-named siblings that cover overlapping ground (NAV deviation, lookup, list), leaving that routing to inference.

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.