Avanza MCP Server

Overview Schema Source Related Servers Discussions Admin

get_stock_quote

Read-onlyIdempotent

Retrieve available stock prices and trading data by Avanza order-book ID, excluding company details. Use the real-time flag and upstream timestamps to verify quote freshness.

Instructions

Get latest available stock prices and trading data, without company details.

Not guaranteed real-time; inspect isRealTime and upstream timestamps. Null is unknown; zero is a reported value.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_book_id`	Yes	Avanza order-book ID from discovery; not the separate instrumentId.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`buy`	No
`last`	No
`sell`	No
`change`	No
`lowest`	No
`spread`	No
`highest`	No
`updated`	No
`isRealTime`	No
`timeOfLast`	No
`changePercent`	No
`totalValueTraded`	No
`totalVolumeTraded`	No
`volumeWeightedAveragePrice`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.1.0Sep 29, 2026
- removedOutput schema / additionalProperties
```
Removed value: -true
```

Changed6 schema fields changedv2.0.0Sep 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / instrument_id
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / order_book_id

Added value: +{
+  "description": "Avanza order-book ID from discovery; not the separate instrumentId.",
+  "minLength": 1,
+  "pattern": "^[0-9]+$",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "instrument_id"
-]New value: +[
+  "order_book_id"
+]

addedOutput schema / description

Added value: +"Latest available stock quote data; inspect isRealTime and source timestamps."

addedOutput schema / properties

Added value: +{
+  "buy": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "change": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "changePercent": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "highest": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "isRealTime": {
+    "anyOf": [
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "last": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "lowest": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "sell": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "spread": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "timeOfLast": {
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "totalValueTraded": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "totalVolumeTraded": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "updated": {
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "volumeWeightedAveragePrice": {
+    "anyOf": [
+      {
+        "type": "number"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  }
+}

First observedv0.1.0Feb 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent, read-only call, so the lower bar applies. The description earns credit by adding real data-quality context beyond the annotations: real-time is not guaranteed, and the null-vs-zero distinction ('Null is unknown; zero is a reported value') meaningfully changes how an agent should interpret results.

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?

Extremely tight: one sentence for the core purpose, then two terse caveat lines that each carry distinct, actionable information. No filler, and the primary purpose is front-loaded.

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

Completeness4/5

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

An output schema exists, so return values need not be documented, and the description usefully references the isRealTime field within it. Combined with annotations covering safety, the definition gives an agent enough to call correctly, though it could name the sibling to use for company data.

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%, and the schema itself explains that order_book_id is the Avanza order-book ID and not instrumentId. The description adds no parameter-level information, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get latest available stock prices and trading data') and carves out scope with 'without company details,' implicitly distinguishing it from get_stock_info. It never names an alternative sibling explicitly, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by 'without company details,' which hints that company metadata belongs to another tool, but the description never states when to prefer this over siblings like get_orderbook, get_recent_trades, or get_stock_info. No explicit when/when-not guidance.

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