Avanza MCP Server

Overview Schema Source Related Servers Discussions Admin

get_certificate_details

Read-onlyIdempotent

Fetch recognized certificate details beyond basic info using an Avanza order-book ID to review certificate terms and status.

Instructions

Get recognized extended certificate details beyond info.

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
`issuer`	No
`trades`	No
`leverage`	No
`direction`	No
`documents`	No
`orderDepth`	No
`collateralValue`	No
`brokerTradeSummaries`	No
`superInterestApproved`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv2.1.0Sep 29, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / brokerTradeSummaries

Added value: +{
+  "items": {
+    "description": "Summary of broker trades for a stock.",
+    "properties": {
+      "brokerCode": {
+        "type": "string"
+      },
+      "brokerName": {
+        "type": "string"
+      },
+      "buyVolume": {
+        "type": "integer"
+      },
+      "netBuyVolume": {
+        "type": "integer"
+      },
+      "sellVolume": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "brokerCode",
+      "sellVolume",
+      "buyVolume",
+      "netBuyVolume",
+      "brokerName"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / collateralValue

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

addedOutput schema / properties / direction

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

addedOutput schema / properties / documents

Added value: +{
+  "anyOf": [
+    {
+      "description": "Public instrument document links.",
+      "properties": {
+        "kid": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "prospectus": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / issuer

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

addedOutput schema / properties / leverage

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

addedOutput schema / properties / orderDepth

Added value: +{
+  "anyOf": [
+    {
+      "description": "Order book depth showing buy and sell orders.",
+      "properties": {
+        "levels": {
+          "default": [],
+          "items": {
+            "description": "Single level in the order book depth.",
+            "properties": {
+              "buySide": {
+                "anyOf": [
+                  {
+                    "description": "Buy or sell side of an order.",
+                    "properties": {
+                      "price": {
+                        "type": "number"
+                      },
+                      "priceString": {
+                        "type": "string"
+                      },
+                      "volume": {
+                        "type": "integer"
+                      }
+                    },
+                    "required": [
+                      "price",
+                      "volume",
+                      "priceString"
+                    ],
+                    "type": "object"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "default": null
+              },
+              "sellSide": {
+                "anyOf": [
+                  {
+                    "description": "Buy or sell side of an order.",
+                    "properties": {
+                      "price": {
+                        "type": "number"
+                      },
+                      "priceString": {
+                        "type": "string"
+                      },
+                      "volume": {
+                        "type": "integer"
+                      }
+                    },
+                    "required": [
+                      "price",
+                      "volume",
+                      "priceString"
+                    ],
+                    "type": "object"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "default": null
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "receivedTime": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / superInterestApproved

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

addedOutput schema / properties / trades

Added value: +{
+  "items": {
+    "description": "Individual trade information.",
+    "properties": {
+      "buyer": {
+        "type": "string"
+      },
+      "buyerName": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "cancelled": {
+        "type": "boolean"
+      },
+      "dealTime": {
+        "type": "integer"
+      },
+      "matchedOnMarket": {
+        "type": "boolean"
+      },
+      "price": {
+        "type": "number"
+      },
+      "seller": {
+        "type": "string"
+      },
+      "sellerName": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "volume": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "buyer",
+      "seller",
+      "dealTime",
+      "price",
+      "volume",
+      "matchedOnMarket",
+      "cancelled"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Addedv2.0.0Sep 15, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description itself adds no behavioral context — nothing about what the extended details include, data freshness, or any side conditions — making it thin even against the lowered bar.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with the verb front-loaded, so it is not bloated. However, the filler word "recognized" and the vague "beyond info" mean the words present do not clearly earn their place.

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 return values need not be described, and annotations cover the safety profile. The main unmet need is differentiation from get_certificate_info and clarity on what "extended" details mean, leaving the definition only minimally adequate.

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?

With a single parameter, 100% schema description coverage, and an explicit schema note distinguishing order_book_id from instrumentId, the schema does the heavy lifting. The description contributes nothing additional 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.

Purpose3/5

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

The verb+resource pair (get certificate details) is identifiable, and "beyond info" hints at a sibling relationship with get_certificate_info. But "recognized extended certificate details" is awkward and ambiguous — it is not clear what "recognized" means or how these details actually differ from get_certificate_info's output.

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?

There is no explicit statement of when to call this versus get_certificate_info or get_certificate_details-like siblings; "beyond info" only loosely implies it is the deeper variant. No prerequisites, ordering, or exclusions are given.

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