Skip to main content
Glama
Sign In
FinanceKit MCP

FinanceKit MCP

by vdalhambra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

compare_assets

Read-only

Compare the performance of multiple stocks including returns, volatility, and key metrics to decide between investment options.

Instructions

Compare performance of multiple stocks/assets over a period.

Returns side-by-side comparison of returns, volatility, and key metrics to help decide between investment options.

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

Input Schema

NameRequiredDescriptionDefault
periodNoComparison period: 1mo, 3mo, 6mo, 1y3mo
symbolsYesComma-separated tickers to compare (e.g., 'AAPL,MSFT,GOOGL')

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0
  2. Removedv1.2.0
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating no side effects. The description adds no further behavioral details beyond the read-only nature, so it does not significantly enhance transparency beyond the annotation.

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?

Description is two brief, front-loaded sentences with no unnecessary words. Every sentence adds value.

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?

With 2 parameters, existing output schema, and readOnlyHint annotation, the description covers the core functionality. Could mention that it is a read operation (but annotation covers that) and hint at the output metrics.

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 100%, and the description paraphrases the parameters (e.g., 'multiple stocks/assets' for symbols, 'over a period' for period) without adding new semantic information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it compares performance of multiple stocks/assets over a period, returning a side-by-side comparison of returns, volatility, and key metrics. This distinguishes it from sibling tools like company_info, price_history, or multi_quote.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description indicates the tool is used 'to help decide between investment options,' providing clear context. However, it does not explicitly state when not to use it or name alternatives among sibling tools.

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

Deploy Server

Other Tools