Avanza MCP Server

Overview Schema Source Related Servers Discussions Admin

get_marketplace_info

Read-onlyIdempotent

Retrieve current marketplace status and trading hours for a specific order-book ID to check whether trading is open before placing orders.

Instructions

Get latest available marketplace status and trading hours.

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
`marketOpen`	Yes
`timeLeftMs`	No
`openingTime`	No
`todayClosingTime`	No
`normalClosingTime`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed7 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: +"Marketplace status and trading hours."

addedOutput schema / properties

Added value: +{
+  "marketOpen": {
+    "type": "boolean"
+  },
+  "normalClosingTime": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "openingTime": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "timeLeftMs": {
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "todayClosingTime": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "marketOpen"
+]
```

First observedv0.1.0Feb 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety and idempotency are covered. The phrase 'latest available' usefully signals fresh, externally-changing data (consistent with openWorldHint), but nothing is said about refresh cadence, caching, or failure when the market is closed.

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?

One tight sentence with no filler and the action front-loaded. It is appropriately sized, though it stops short of the detail that would make it a 5.

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

Completeness3/5

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

An output schema exists, so explaining return values is not required, and annotations carry the safety profile. Still, for an open-world read tool sharing a crowded namespace with get_stock_info/get_orderbook, the definition omits when this tool is the right choice.

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 single parameter is fully documented in the schema, including the important distinction from instrumentId. The description adds nothing about the parameter, so the baseline 3 applies.

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 clear verb (Get) and resource (marketplace status and trading hours), so the agent knows what data comes back. However, it never distinguishes this from sibling tools like get_stock_info or get_orderbook, which also return instrument-level state, leaving the agent to infer the boundary.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites, and no alternatives. With ~35 sibling tools covering instrument data, the absence of any routing cue is a real gap.

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