Skip to main content
Glama
portfolio-signals-mcp

portfolio-signals-mcp

weekly_digest

Generate a portfolio check-in report with 1-week and 1-month returns plus indicator readings per holding, enabling recurring signal reviews in one call.

Instructions

One-call weekly portfolio report: 1-week and 1-month returns plus indicator readings for each holding. Ideal for a recurring 'weekly portfolio signals' check-in.

Args: tickers: Portfolio symbols, e.g. ['AAPL', 'NVDA', 'VOO'].

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": {
      "tickers": "<tickers>"
    },
    "name": "weekly_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses that this is a batched one-call operation returning per-holding returns and indicator readings, implying a read-only data fetch, but says nothing about behavior for invalid or empty ticker lists, list-size limits, or whether the indicator readings match those from get_technical_signals.

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 is front-loaded and short, with the return contents stated first and the use case second. There is mild redundancy in repeating 'weekly' across the name and two sentences, but no filler.

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, no-output-schema tool, the description covers what the agent most needs: what comes back (1W and 1M returns plus indicators) and the shape of the argument. Remaining gaps are secondary details like symbol limits and indicator definitions rather than anything blocking a correct call.

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?

Schema coverage is 0%, so the description must compensate, and it partly does by defining tickers as portfolio symbols with a concrete example array. It omits practical semantics such as maximum symbol count, duplicate handling, and whether order affects the output.

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 artifact (a weekly portfolio report) and enumerates its contents: 1-week and 1-month returns plus indicator readings for each holding. That distinguishes it in practice from single-symbol siblings like get_quote and get_technical_signals, though it never names them explicitly.

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?

"Ideal for a recurring 'weekly portfolio signals' check-in" gives a positive use context, which is real but thin. There is no statement of when not to use it, nor any routing to get_quote for single symbols or get_technical_signals for deeper indicator work, so the agent must infer the boundary.

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