Skip to main content
Glama
portfolio-signals-mcp

portfolio-signals-mcp

compare_tickers

Compare total returns across multiple tickers over a chosen period (1mo–5y). Failed symbols are reported individually with error details instead of breaking the whole comparison.

Instructions

Compare total returns of multiple tickers over a period.

A symbol that fails is reported with error and error_type instead of failing the whole call.

Args: tickers: List of symbols, e.g. ['AAPL', 'MSFT', 'VOO']. period: Lookback window for the returns.

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": "compare_tickers"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo3mo
tickersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

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 one genuinely important behavior: per-symbol failures return error/error_type rather than aborting the call. It says nothing about data source, rate limits, or the shape of the returned comparison (e.g., metric fields per ticker), leaving notable gaps for a no-annotation tool.

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 and the partial-failure caveat are front-loaded and earn their place. The Args block largely restates schema fields, though the ticker example is useful, so there is mild redundancy but no bloat.

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 simple two-parameter tool with no output schema and no annotations, the definition covers the core behavior and the failure mode. It remains incomplete on what the comparison actually returns (which return metrics, sorting, per-symbol structure), which matters more given the absence of an output schema.

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 description coverage is 0%, so the description must compensate. It documents both parameters, including a concrete ticker-list example ('AAPL','MSFT','VOO'), but 'Lookback window for the returns' adds little over the parameter name and omits the allowed enum values and the 3mo default that the schema specifies.

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 states a specific verb and resource — 'Compare total returns of multiple tickers over a period' — which clearly separates it from single-symbol siblings like get_quote. It stops short of explicitly naming or contrasting any alternative, so it is clear but not fully differentiated.

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?

There is no explicit when-to-use guidance, no prerequisites, and no statement of when another tool would be preferable (e.g., a single quote lookup). Usage is only implied by 'multiple tickers'.

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