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. Symbols that collide with tokenized-stock proxies on the crypto side (ALAB, LITE, NBIS, GLW, CBRS, DRAM, AIPO) resolve to the listed instrument, never the token; qualifying as NASDAQ:X / X.US does the same explicitly. base_currency defaults to USD; 'native' returns unconverted quotes.

Input Schema

TableJSON 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

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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 already declare readOnly=true/openWorld=true, so the safety profile is covered; the description goes well beyond that. It discloses the resolution model (matched_by values, candidates, mismatch reporting), that contradictory hints are reported rather than silently overridden, the tokenized-stock collision policy, that asset.isin is only populated from a hint or provider profile and is not looked up, and the 'native' no-conversion behavior.

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 carries information, but the body is a single dense block that packs resolution, hints, token collisions, and currency handling into one long paragraph. It earns its length given the tool's complexity, though it could be more scannable.

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?

An output schema exists to cover return values, and the description fully addresses the hard part of this tool — how symbols resolve, what the hints do, and how collisions with tokenized proxies are handled. 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.

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description adds interpretation beyond the schema: that a contradicting isin/exchange/asset_class hint is surfaced as resolution.mismatch rather than overridden, and that base_currency='native' leaves quotes unconverted with fx null. These reinforce and extend, rather than merely restate, the schema.

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 concrete verb and resource ('Live prices for one or more holdings') and immediately frames the distinctive behavior ('the answer shows its work'). An agent can tell it apart from sibling tools like get_etf_profile or score_position_drift without opening the 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?

Gives clear conditions for using the per-holding hints (isin, exchange, asset_class) and for forcing a listed instrument over a tokenized proxy (qualifying as NASDAQ:X / X.US). It stops short of explicitly routing the agent among siblings, but the usage context for its own parameters is well specified.

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?