Skip to main content
Glama
Sign In
realmarket-mcp

realmarket-mcp

by itu-itis24-iyigun24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

compare_assets

Read-onlyIdempotent

Line up 2 to 10 assets over one date range to see total and annualized return, volatility, and maximum drawdown for each, plus rankings in a chosen currency.

Instructions

Put 2 to 10 assets side by side over one common date window: total and annualized return, volatility and maximum drawdown for each. Use it to compare assets or an asset against an index. Returns are nominal, each in its own currency; assets priced in different currencies (a share in TRY, gold in USD) are also measured in one currency and ranked in it. Ratios are fractions (0.12 means 12%).

Input Schema

NameRequiredDescriptionDefault
endNoOptional ISO end date; defaults to today.
startNoOptional ISO start date, e.g. '2023-01-01'.
periodNoLookback ending at `end`. Ignored when `start` is given.1y
symbolsYes2 to 10 symbols from search_assets.
currencyNoCurrency to compare in when the assets are priced in different currencies, e.g. 'USD'. Default: TRY when one of them is priced in TRY, else the first asset's currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.9
    • addedInput schema / properties / currency
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Currency to compare in when the assets are priced in different currencies, e.g. 'USD'. Default: TRY when one of them is priced in TRY, else the first asset's currency.",
+  "title": "Currency"
+}
    • addedInput schema / properties / period / anyOf
      Added value: +[
+  {
+    "enum": [
+      "1m",
+      "3m",
+      "6m",
+      "ytd",
+      "1y",
+      "3y",
+      "5y",
+      "10y",
+      "max"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / period / enum
      Removed value: -[
-  "1m",
-  "3m",
-  "6m",
-  "ytd",
-  "1y",
-  "3y",
-  "5y",
-  "10y",
-  "max"
-]
    • removedInput schema / properties / period / type
      Removed value: -"string"
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, idempotent). The description adds useful non-obvious behavior: nominal returns, per-currency measurement, the cross-currency normalization and ranking rule, and the fraction convention for ratios. It does not cover error behavior or pagination, but adds real context beyond the annotations.

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?

Three tight sentences: what it does and the metric set first, the comparison use case second, and the currency/units caveats last. Every sentence carries information and nothing is repeated from the schema.

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 no output schema, the description correctly carries the burden of describing returns, volatility, drawdown, currency handling, and ratio units, which it does well. Minor gaps remain (e.g., behavior on invalid symbols or mixed-date-range failures), but the essential call-time information is present.

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%, so all five parameters are already documented in the schema, including the currency default rule. The description reinforces the currency behavior and the fraction convention but adds little syntax or format detail beyond what the schema already provides; baseline 3 is appropriate.

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?

Names a specific verb (compare), the resource (2–10 assets), the common date window, and the exact metrics returned (total and annualized return, volatility, maximum drawdown). The nominal-return caveat implicitly distinguishes it from compare_real_return, so an agent can tell it apart from siblings without opening a schema.

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?

'Use it to compare assets or an asset against an index' gives clear context for when this tool applies. It does not name the alternative (compare_real_return) or state when-not-to-use conditions, so it falls short of full routing guidance.

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