Avanza MCP Server

Overview Schema Source Related Servers Discussions Admin

get_instrument_by_order_book_id

Read-onlyIdempotent

Resolve an exact Avanza order-book ID to its instrument details, matching only the precise ID among up to 50 candidates to avoid incorrect substitutions.

Instructions

Match an exact order_book_id among at most 50 search candidates.

Search is not authoritative: failure to match does not prove the ID is invalid. Never substitutes the first or a similarly named search result.

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
`isin`	No
`name`	Yes
`type`	Yes
`currency`	No
`exchange`	Yes
`order_book_id`	Yes	Avanza order-book ID from discovery; not the separate instrumentId.

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv2.0.0Sep 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / order_book_id / description

Added value: +"Avanza order-book ID from discovery; not the separate instrumentId."

addedInput schema / properties / order_book_id / minLength
```
Added value: +1
```
addedInput schema / properties / order_book_id / pattern
```
Added value: +"^[0-9]+$"
```

addedOutput schema / description

Added value: +"Curated instrument identity; presentation and highlighting are excluded."

addedOutput schema / properties / currency

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

addedOutput schema / properties / exchange

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

addedOutput schema / properties / isin

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

addedOutput schema / properties / name
```
Added value: +{
+  "type": "string"
+}
```

addedOutput 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"
+}

removedOutput schema / properties / result

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / type
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "order_book_id",
+  "name",
+  "type",
+  "exchange"
+]

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedv0.1.0Feb 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly, openWorld, and idempotent behavior. The description adds concrete open-world semantics: failure to match is not proof of invalidity, and the tool will not fall back to a similar result. This goes beyond the annotations and prevents a common agent misinterpretation.

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?

Three short sentences, front-loaded with the core matching operation and followed by two necessary caveats. There is no filler or redundant restatement of the tool name or schema.

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?

With one well-documented parameter, an output schema already present, and annotations covering safety and open-world behavior, the description adds exactly the missing operational caveats. Nothing essential for calling the tool correctly is absent.

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 coverage is 100% and the parameter description already clarifies that order_book_id is the Avanza discovery ID, distinct from instrumentId. The tool description does not add new parameter-level meaning; 'exact' and 'at most 50 candidates' describe behavior more than parameter semantics.

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 states a specific verb ('Match') and a precise resource scope ('exact order_book_id among at most 50 search candidates'). It also draws a clear behavioral boundary by warning that it never substitutes the first or a similarly named search result, which distinguishes it from broad search-oriented siblings.

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?

The intended use is clear: call this tool when you have an exact order_book_id from discovery and want to match it exactly. The description does not explicitly name an alternative tool or state when-not-to-use, but the exact-match language and candidate cap provide sufficient routing context.

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