Skip to main content
Glama

finwire.pl - Polish financial data

Brokerage account fees

get_broker_fees
Read-onlyIdempotent

Use for brokerage account fees. Fees of brokers available to Polish investors from their official fee tables: online order commission on Warsaw (GPW), US and German stocks and ETFs, account and currency conversion fees, IKE/IKZE and investor protection, with the fee table URL and the date it was last confirmed. Facts only, no ranking or recommendation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_broker_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
brokerNoFilter by broker name or id, e.g. "XTB", "mbank".
marketNoShow the commission of one market only.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds meaningful context beyond them: the data provenance (official fee tables), coverage scope, and the explicit stance that results are facts without ranking or recommendation, which shapes how an agent should present the output.

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?

Two compact sentences, front-loaded with the purpose followed by a coverage list and the neutrality caveat. The middle list is dense but each item earns its place by telling the agent what fee categories exist; nothing is padding.

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?

With an output schema present, return values need not be explained, and annotations cover safety. For a two-optional-parameter lookup tool the description is nearly complete; only the absence of explicit framing against sibling financial-data tools keeps it short of full marks.

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?

Both parameters are fully documented in the schema, so the baseline is 3. The mention of GPW, US and German markets loosely maps to the market enum values and the broker filter is implied by "fees of brokers", but no format or matching semantics are added beyond the schema.

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?

The description names the resource and enumerates exactly what is covered: online order commissions on GPW, US and German stocks and ETFs, account and currency conversion fees, IKE/IKZE and investor protection, plus source URL and confirmation date. That is far more specific than the title, though it never states a verb or contrasts itself with the other financial-data siblings.

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 opening "Use for brokerage account fees" is a minimal usage cue, and the "Facts only, no ranking or recommendation" line implicitly sets the tool apart from advisory tools. There is no explicit when-to-use vs. when-not guidance and no sibling such as the bank-rate or currency-rate tools is named as an alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.