Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

tokenized_stock_model_portfolio

Read-onlyIdempotent

Generate model portfolio weights and rebalance suggestions for up to 12 tokenized stock symbols using balanced, low-staleness NAV, or diversified objectives.

Instructions

Model portfolio / rebalance suggestions (weights only — no orders).

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

Cost: $0.08 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_model_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes
objectiveNobalanced
current_weightsNo

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 readOnlyHint, idempotentHint, non-destructive and open-world, so safety is covered. The description adds genuinely new behavior: output is weights only, no orders are placed, jurisdictional eligibility for U.S. persons, and a per-call cost of $0.08 — the cost and eligibility disclosures are exactly the kind of context annotations cannot carry.

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 core purpose is front-loaded in the first sentence, with the legal and pricing notes following in compact, clearly separated lines. Every element earns its place; there is no filler.

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, the description should say more about the return shape than 'weights only', and it leaves all three parameters undocumented. It does cover the eligibility, cost, and no-execution caveats well, so it is adequate for a research tool but incomplete for its parameter surface.

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% across three parameters, including a nested free-form object, so the description must compensate and does not. It never explains what 'symbols' expects (up to 12 tickers), what the 'objective' enum values like 'low_staleness_nav' mean, or how 'current_weights' is consumed to produce a rebalance.

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 names a specific output (model portfolio / rebalance weight suggestions) and explicitly bounds it ('weights only — no orders'), which distinguishes it from execution or trading siblings. It stops short of saying what the input symbols represent (a universe) or what the weights map onto, so the picture is clear but not fully specified.

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 boundaries are framed as restrictions rather than routing: 'RESEARCH ONLY', 'no trading, execution, custody, or swaps', and the U.S. persons exclusion. Those tell an agent when NOT to use it, but no sibling or alternative is named and no positive when-to-use condition is given.

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