Skip to main content
Glama
AnteWall

Avanza MCP Server

by AnteWall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_fund_description

Read-onlyIdempotent

Retrieves a fund's investment description and category explanation from Avanza using an order-book ID, helping you understand the fund's focus.

Instructions

Get the fund's investment description and category explanation.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
headingYes
responseYes
detailedCategoryDescriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • removedOutput schema / additionalProperties
      Removed value: -true
  2. Changed7 schema fields changedv2.0.0
    • 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: +"Fund description and category information."
    • addedOutput schema / properties
      Added value: +{
+  "detailedCategoryDescription": {
+    "type": "string"
+  },
+  "heading": {
+    "type": "string"
+  },
+  "response": {
+    "type": "string"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "response",
+  "heading",
+  "detailedCategoryDescription"
+]
  3. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that — no note about response shape, static vs. dynamic content, or locale/language of the descriptive text.

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?

A single ten-word sentence with no filler and the resource stated immediately. It is efficient and front-loaded, though its brevity borders on under-specification rather than model concision.

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?

For a single-parameter read tool with a full annotation set and an output schema (so return values need not be described), the description covers what an agent needs to invoke it. It would be a 5 only if it clarified the boundary with other fund-information siblings.

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 disambiguates the key point ('Avanza order-book ID from discovery; not the separate instrumentId'). With one fully documented parameter, the baseline of 3 applies since the description adds no additional parameter meaning.

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?

Names a specific verb ('Get') and a specific resource pair (the fund's investment description and category explanation), which distinguishes it from data-returning siblings like get_fund_holdings, get_fund_chart, or get_fund_info. It stops short of explicitly contrasting itself with those siblings, but the resource is concrete enough to route correctly.

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 statement of when to use this tool versus the many other fund tools (get_fund_info, get_fund_sustainability, get_fund_details-adjacent siblings). An agent must infer from the resource name alone that this returns narrative/descriptive text rather than numeric fund data.

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