Skip to main content
Glama

alpha-sentinel-mcp

tokenized_stock_model_portfolio

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 observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: pure computation with no trading/execution/custody/swaps, an eligibility restriction (not offered to U.S. persons), and a per-call cost of $0.08. What it omits is equally behavioral — no statement of idempotency, determinism, latency, or what the returned weights structure actually looks like.

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 sentence is front-loaded and the disclaimers and cost are packed into short, scannable lines rather than prose. The repeated negative framing (no orders / no trading, execution, custody, swaps) is slightly redundant but each line is short and earns its place as a guardrail.

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 three-parameter tool with a nested object, an enum, and no output schema, the description covers safety and cost but not the return shape beyond "weights only", and does not explain the objective values or the current_weights structure. An agent could invoke it, but would be guessing at what it gets back and how to set the non-required parameters.

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 object, yet the description says nothing about symbols (count limits), the objective enum choices (balanced / low_staleness_nav / diversified), or what current_weights is keyed by and used for. Only a weak hint ("weights only") relates to the weight-based input/output, leaving the agent to infer everything else from raw 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?

"Model portfolio / rebalance suggestions (weights only — no orders)" states the resource produced (portfolio weights) and explicitly bounds scope to non-execution. It distinguishes itself from execution-oriented tools, though it does not name a specific sibling it is meant to be used instead of.

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 context is only implied: the RESEARCH ONLY framing and "no orders" tell the agent this is an analytics step, not a trading step. There is no explicit when-to-use condition, no mention of when to prefer calculate_risk_score or tokenized_stock_research_brief, and no stated preconditions such as resolving symbols via tokenized_stock_lookup first.

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.