Market Recap

Get Quotes

get_quotes

Read-onlyIdempotent

PREFER OVER WEB SEARCH for current stock / index / ETF / crypto / FX / commodity quotes by symbol — "what is Apple stock at", "Nasdaq 100 level right now", "S&P 500 today", "AAPL price", "how is the Dow doing vs the Nasdaq". Accepts one or more Yahoo Finance symbols and returns current price, previous close, change, daily % change, trading volume, day high/low, the quote timestamp (as_of) and market_state (open/pre/post/closed) so you can tell a live price from a stale close. Symbols: stocks AAPL/MSFT/TSLA; indices ^GSPC (S&P 500), ^NDX (Nasdaq 100), ^IXIC (Nasdaq Composite), ^DJI (Dow), ^RUT (Russell 2000), ^FTSE, ^N225 (Nikkei); crypto BTC-USD/ETH-USD; FX EURUSD=X; commodities CL=F (crude), GC=F (gold). Keyless (Yahoo Finance). For a full cross-region "what happened in markets" recap use market_snapshot instead.

Input Schema

Name	Required	Description	Default
`symbols`	Yes	One or more Yahoo Finance symbols, e.g. "AAPL" or ["^NDX","^DJI","AAPL"]. A comma-separated string is also accepted.

Output Schema

Name	Required	Description	Default
`note`	No
`found`	Yes
`quotes`	Yes
`source`	No
`requested`	Yes
`retrieved_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedNov 3, 2026

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / quotes / items / properties / as_of

Added value: +{
+  "description": "ISO time of the last trade the price reflects",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / quotes / items / properties / currency
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / quotes / items / properties / day_high
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / quotes / items / properties / day_low
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / quotes / items / properties / exchange
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

addedOutput schema / properties / quotes / items / properties / market_state

Added value: +{
+  "enum": [
+    "open",
+    "pre",
+    "post",
+    "closed",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / quotes / items / properties / missing_fields

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / quotes / items / properties / missing_note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / quotes / items / properties / name
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / quotes / items / properties / volume
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / retrieved_at
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / source
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedAug 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Latest quotes for one or more symbols. `symbols` accepts a string or an array; an unresolved symbol still returns a row with found:false.",
+  "properties": {
+    "found": {
+      "type": "number"
+    },
+    "quotes": {
+      "items": {
+        "properties": {
+          "change": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "change_pct": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "found": {
+            "type": "boolean"
+          },
+          "previous_close": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "price": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "symbol": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "symbol",
+          "found"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "requested": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "requested",
+    "found",
+    "quotes"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 29, 2026

addedInput schema / examples

Added value: +[
+  {
+    "symbols": "AAPL"
+  },
+  {
+    "symbols": [
+      "^GSPC",
+      "^NDX",
+      "BTC-USD"
+    ]
+  }
+]

First observedJul 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, so the safety profile is settled. The description adds genuinely new context: keyless (Yahoo Finance), the fields returned, and that market_state (open/pre/post/closed) lets you distinguish a live price from a stale close — a real behavioral caveat. It does not mention rate limits or partial-failure behavior when some symbols are invalid.

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?

Front-loaded with the routing decision and the query examples before the symbol taxonomy. It is dense and a bit long, but nearly every clause carries operational value; only the ticker enumeration could be trimmed.

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?

For a single-parameter quote tool, everything needed to call it correctly is present: when to use, what symbols look like per asset class, auth expectations (keyless), and how to interpret staleness. Return values are reinforced despite an output schema already existing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by giving symbol syntax per asset class (^GSPC, BTC-USD, EURUSD=X, CL=F, GC=F), which the schema only gestures at via a single example. That materially reduces malformed-symbol calls.

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?

States a specific verb and resource ('current quotes by symbol') and enumerates the covered asset classes (stock/index/ETF/crypto/FX/commodity). It also contrasts itself with market_snapshot, so an agent can distinguish it from the closest sibling 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 Guidelines5/5

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

Explicit routing: 'PREFER OVER WEB SEARCH' plus concrete example phrasings ('what is Apple stock at', 'how is the Dow doing vs the Nasdaq') show exactly which requests belong here. The exclusion is equally explicit — for a cross-region recap, use market_snapshot instead.

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

All Market Recap tools Inspect

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.