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), 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.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral context: resolution logic (matched_by isin|qualified_symbol|bare_symbol), mismatch reporting rather than silent overrides, the tokenized-stock collision policy, and FX conversion behavior. This goes well beyond what annotations provide.

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?

The description is dense but well-organized, front-loading the core purpose and then layering resolution details, collision handling, and currency behavior. Every sentence adds information, though the tokenized-stock list and resolution taxonomy make it longer than strictly necessary. The structure is logical and 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?

Given the output schema exists (so return values are documented elsewhere), the description covers all decision-relevant context: what the tool does, how resolution works, how to force a path, how currency conversion behaves, and how conflicts are handled. An agent has everything needed to invoke it correctly and interpret results.

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 schema already documents all parameters thoroughly. The description adds value by explaining the resolution semantics (hints narrow resolution, contradictions are reported), the collision policy for specific symbols, and the base_currency 'native' behavior. It doesn't repeat schema details but enriches them with behavioral context.

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 a clear verb and resource: 'Live prices for one or more holdings' and immediately distinguishes itself from siblings by emphasizing it 'shows its work' with resolution details, FX, and per-holding breakdowns. It is specific about what it returns (price, value, day change, resolution, quote, fx) and how it handles ambiguous tickers, making it unmistakable among the many get_* siblings.

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?

The description explicitly states when to use this tool (live prices for holdings) and provides detailed guidance on how to disambiguate symbols, including the tokenized-stock collision list and the NASDAQ:X / X.US qualification. It also explains base_currency behavior and the 'native' option. While it doesn't name a specific alternative sibling, the guidance is so specific that an agent can confidently select it for price queries.

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?