Skip to main content
Glama

FolioFact

by com.foliofact
OverviewDiscussionsAdmin

Compare stocks side by side

compare_stocks
Read-onlyIdempotent

Aligned multi-stock comparison: valuation, latest financial point, fund conviction, and insider activity. Requires FolioFact Pro.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickersYesComma-separated tickers (2–6, dots allowed).
insider_windowNoInsider activity window.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
columnsYes
tickersYes
provenanceYes
insider_windowYes
unknown_tickersYes
submitted_tickersYes
insider_window_labelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / columns / items / properties / valuation_basis
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "accession_number": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "calculation_version": {
+      "type": "string"
+    },
+    "cash_flow_period": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": "string"
+    },
+    "estimated": {
+      "type": "boolean"
+    },
+    "ev_unavailable_reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "mapping_sources": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "measurement": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price_on": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "shares_on": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "statement_on": {
+      "format": "date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "unavailable_reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "statement_on",
+    "shares_on",
+    "price_on",
+    "measurement",
+    "estimated",
+    "description",
+    "unavailable_reason",
+    "ev_unavailable_reason",
+    "accession_number",
+    "source_url",
+    "mapping_sources",
+    "calculation_version",
+    "cash_flow_period"
+  ],
+  "type": "object"
+}
    • changedOutput schema / properties / columns / items / required
      Previous value: -[
-  "ticker",
-  "name",
-  "listing",
-  "market_cap",
-  "enterprise_value",
-  "ocf_ev_yield",
-  "fcf_ev_yield",
-  "price_basis_kind",
-  "valuation_observed_at",
-  "financial_point",
-  "fund_summary",
-  "insider_summary"
-]New value: +[
+  "ticker",
+  "name",
+  "listing",
+  "market_cap",
+  "enterprise_value",
+  "ocf_ev_yield",
+  "fcf_ev_yield",
+  "price_basis_kind",
+  "valuation_observed_at",
+  "financial_point",
+  "fund_summary",
+  "insider_summary",
+  "valuation_basis"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / columns / items / properties / listing
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "disclosure_note": {
+          "type": "string"
+        },
+        "event_type": {
+          "enum": [
+            "ipo",
+            "direct_listing",
+            "spin_off"
+          ],
+          "type": "string"
+        },
+        "listed_on": {
+          "format": "date",
+          "type": "string"
+        },
+        "recently_listed": {
+          "type": "boolean"
+        },
+        "source_url": {
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "listed_on",
+        "event_type",
+        "recently_listed",
+        "source_url",
+        "disclosure_note"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / columns / items / required
      Previous value: -[
-  "ticker",
-  "name",
-  "market_cap",
-  "enterprise_value",
-  "ocf_ev_yield",
-  "fcf_ev_yield",
-  "price_basis_kind",
-  "valuation_observed_at",
-  "financial_point",
-  "fund_summary",
-  "insider_summary"
-]New value: +[
+  "ticker",
+  "name",
+  "listing",
+  "market_cap",
+  "enterprise_value",
+  "ocf_ev_yield",
+  "fcf_ev_yield",
+  "price_basis_kind",
+  "valuation_observed_at",
+  "financial_point",
+  "fund_summary",
+  "insider_summary"
+]
  3. Changed3 schema fields changed
    • addedOutput schema / properties / columns / items / properties / price_basis_kind
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "daily_close",
+        "intraday",
+        "implied_13f"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / columns / items / properties / valuation_observed_at
      Added value: +{
+  "format": "date-time",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / columns / items / required
      Previous value: -[
-  "ticker",
-  "name",
-  "market_cap",
-  "enterprise_value",
-  "ocf_ev_yield",
-  "fcf_ev_yield",
-  "financial_point",
-  "fund_summary",
-  "insider_summary"
-]New value: +[
+  "ticker",
+  "name",
+  "market_cap",
+  "enterprise_value",
+  "ocf_ev_yield",
+  "fcf_ev_yield",
+  "price_basis_kind",
+  "valuation_observed_at",
+  "financial_point",
+  "fund_summary",
+  "insider_summary"
+]
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar for extra disclosure is lower. The description adds a valuable access constraint (Requires FolioFact Pro) and explains what kind of data is aligned across stocks. No contradiction with 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?

One dense sentence front-loads the core behavior, lists the comparison content, and ends with the Pro requirement. Every clause earns its place and there is no redundant restatement of the tool name or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema, 100% parameter coverage, and read-only/idempotent annotations, the description provides the missing contextual pieces: the multi-stock alignment, the content categories, and the subscription requirement. Nothing an agent needs to invoke it correctly is missing.

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 the schema fully documents tickers (comma-separated, 2–6, dots allowed) and insider_window (90d/1y/all). The description adds only high-level context like 'insider activity' and does not need to repeat parameter syntax; 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?

The description opens with 'Aligned multi-stock comparison', giving a specific operation and resource, and names the comparison dimensions (valuation, latest financial point, fund conviction, insider activity). This clearly distinguishes it from single-stock siblings like get_stock, stock_financials, and stock_insiders.

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?

It gives a clear use context: choose this when you need an aligned comparison across multiple tickers. It also states the FolioFact Pro requirement as a gate. It does not explicitly name alternatives or when-not-to-use conditions, so it stops short of a 5.

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

All FolioFact toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources