Skip to main content
Glama
AnteWall

Avanza MCP Server

by AnteWall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_marketmaker_chart

Read-onlyIdempotent

Retrieve raw OHLC and market-maker data for traded products with offset/limit pagination. Supports analysis of market-maker activity and price charts for non-stock/fund instruments.

Instructions

Get raw OHLC and market-maker data for traded products, not stock/fund charts.

Both arrays are independently sliced with the same offset/limit in source order; their metadata counts are separate. No point alignment, aggregation or unit conversion is inferred. Upstream fields are under data, separate from wrapper pagination keys. Not guaranteed real-time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
time_periodNotoday
order_book_idYesAvanza order-book ID from discovery; not the separate instrumentId.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesPrice chart data response. Used for both stock charts and marketmaker charts.
paginationYes
marketMakerPaginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • removedOutput schema / properties / data / additionalProperties
      Removed value: -true
    • changedOutput schema / properties / data / properties / marketMaker / anyOf
      Previous value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "description": "Reported market-maker bid and ask at one timestamp.",
+      "properties": {
+        "buy": {
+          "type": "number"
+        },
+        "sell": {
+          "type": "number"
+        },
+        "timestamp": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "buy",
+        "sell",
+        "timestamp"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / data / properties / metadata / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / data / properties / metadata / properties / resolution / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / data / properties / ohlc / items / additionalProperties
      Removed value: -true
  2. Addedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral value beyond them: independent slicing of two arrays with shared offset/limit, no inferred alignment/aggregation/unit conversion, and an explicit "not guaranteed real-time" caveat. It omits auth/rate-limit context but the data-semantics disclosure is strong.

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?

Purpose is front-loaded in the first clause, and the following sentences each add distinct semantic information. Dense and slightly technical but no wasted sentences.

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-value explanation is not required, and the description still adds the wrapper/data separation and pagination key location. Combined with annotations covering safety, the definition is nearly complete, with only parameter-level detail (time_period) left thin.

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 only 25% (only order_book_id is documented), so the description should compensate. It clarifies that offset/limit slice both arrays independently, but says nothing about the time_period enum behavior (required enum, especially) or the limit maximum of 100, leaving meaningful gaps.

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?

States a specific verb and resource (raw OHLC and market-maker data) and explicitly differentiates from the sibling chart tools ("not stock/fund charts"). An agent can distinguish this from get_stock_chart and get_fund_chart without opening either schema.

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?

The negative scoping ("not stock/fund charts") tells the agent when NOT to use this tool, which is useful, but no alternative tool is named and there is no positive when-to-use criterion. Usage is only implied via the exclusion.

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

Deploy Server

Other Tools