jawz

Get prices

get_prices

Read-only

Live prices for one or more holdings, and the answer shows its work. Resolves raw tickers (stocks, ETFs, crypto, international listings) and returns price, value, and day change per symbol, plus per holding: what it resolved to (asset: type, exchange, ISIN, provider id; asset.isin is filled when you pass an isin hint or the provider profile carries one, and is null otherwise — it is not looked up), how surely (resolution: matched_by isin|qualified_symbol|bare_symbol, candidates, mismatch against the caller's hints), the native quote with its own time (quote), the FX rate actually applied, dated and sourced (fx), and the position value native and in the base currency. Optional per-holding hints — isin (equities/ETFs/funds), exchange, asset_class — narrow resolution; a hint that contradicts the result is reported, not silently overridden. A bare ticker is resolved listing first: when the same symbol is both a US listing and a crypto token that is not a known major coin (HOOD, MSTR, and tokenized-stock proxies such as ALAB, LITE, NBIS), it prices the listing, never the token; the token is priced only when no such listing exists. A known major coin that shares its symbol with a well-known US listing (STX is Stacks and Seagate) stays the coin, with a line warning that names the listing and how to get it (qualify it, or asset_class 'equity'). A bare ticker shared by differently named funds on other venues (DRAM) is priced with a line warning naming the alternatives and their qualified symbols, counted in resolution.candidates. Qualifying as NASDAQ:X / X.US picks the US listing explicitly. Line warnings are in each holding's warning; a summary is in the top-level warnings. base_currency defaults to USD; 'native' returns unconverted quotes.

Input Schema

Name	Required	Description	Default
`holdings`	Yes	Portfolio holdings to analyze
`base_currency`	No	Currency for price, value and totalValue. Omit for USD (default). 'native' or null: no conversion — each line is stated in its quote currency and fx is null.

Output Schema

Name	Required	Description	Default
`holdings`	No
`warnings`	No
`timestamp`	No
`totalValue`	No
`base_currency`	No
`terms_glossary`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedOutput schema / properties / base_currency

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed4 schema fields changedSep 14, 2026

addedInput schema / properties / base_currency

Added value: +{
+  "description": "Currency for price, value and totalValue. Omit for USD (default). 'native' or null: no conversion — each line is stated in its quote currency and fx is null.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / holdings / items / properties / asset_class

Added value: +{
+  "description": "Optional. 'equity' | 'etf' | 'fund' force the listed-instrument path; 'crypto' forces the token path. Reported as resolution.mismatch when the result disagrees.",
+  "enum": [
+    "equity",
+    "etf",
+    "fund",
+    "crypto",
+    "commodity",
+    "other"
+  ],
+  "type": "string"
+}

addedInput schema / properties / holdings / items / properties / exchange

Added value: +{
+  "description": "Optional exchange hint — NASDAQ, NYSE, NYSEARCA, XETRA, OSL, MIL, LSE, PAR, AMS, SWX, HKG, TSX, ASX. Narrows a bare symbol to a venue; a non-US venue prices the local listing.",
+  "type": "string"
+}

addedInput schema / properties / holdings / items / properties / isin

Added value: +{
+  "description": "Optional ISIN (equities, ETFs, funds — crypto has none). When present, resolution goes by ISIN first; the exchange hint picks the listing when the ISIN trades on several.",
+  "type": "string"
+}

Changed2 schema fields changedSep 6, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / terms_glossary

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare readOnly/openWorld/non-destructive, yet the description adds substantial behavior beyond them: contradictory hints are reported rather than silently overridden, asset.isin is only filled from a hint or provider profile (never looked up), bare-ticker vs token ambiguity is resolved with explicit rules, and line/top-level warnings are described. This is unusually rich disclosure for a read-only 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?

Purpose is front-loaded and every clause is substantive, but the body is dense and parenthetical-heavy (e.g. the enumerated tokenized-stock proxies), which strains readability for a definition of this length. It earns its space on content but could be tightened structurally.

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?

Even though an output schema exists — which would relieve the description of return-value duty — it still describes the response shape (resolution, quote, fx, per-holding warnings) and closes the resolution-ambiguity cases an agent would otherwise get wrong. Nothing needed to call it correctly is missing.

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 would be 3, but the description adds cross-cutting semantics the schema does not carry on its own: how hints interact with each other and the result, that base_currency defaults to USD while 'native' returns unconverted quotes, and how a mismatched hint surfaces in resolution.mismatch.

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+resource ('Live prices for one or more holdings') and immediately scopes the return: price, value, day change per symbol plus per-holding resolution/quote/FX detail. It is unmistakable against siblings like get_etf_profile or get_macro_regime, none of which price holdings.

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?

Gives strong conditional guidance on how to invoke it correctly — qualify a ticker as NASDAQ:X / X.US to force a US listing, use asset_class 'equity' to override a same-symbol token, pass isin/exchange hints to narrow resolution. It does not name a sibling alternative or state an exclusion, but no sibling overlaps its function, so the remaining gap is minor.

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

All jawz 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.

Resources

Need Help?