IDF Metale — gold & silver bullion (Poland)

Server Details

Polish gold/silver bullion dealer: live PLN prices, stock, buyback prices, guides. Read-only.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 60 days
Last Tested: 2026-10-16 11:48
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A3.9/5.0

Scored 2026-09-29 22:50 across 9 tools

Disambiguation4/5

Most tools target distinct facets: availability, live sale price, buyback price, product details, taxonomy, and knowledge. There is some overlap because get_product aggregates live price and availability, which get_live_price and check_availability also expose, but the descriptions clearly state their narrower purposes.

Naming Consistency5/5

All tool names use a consistent snake_case verb_noun pattern: check_availability, get_buyback_price, get_live_price, get_product, list_brands, list_categories, read_knowledge, search_knowledge, search_products. The verbs are predictable and readable.

Tool Count5/5

Nine tools are well-scoped for a bullion catalog and knowledge server. Each tool covers a distinct operation, and there are no redundant or filler tools.

Completeness4/5

The surface covers product search and details, live pricing, availability, buyback pricing, brands, categories, and knowledge lookup. Order finalization is intentionally absent due to KYC/AML, but minor gaps remain such as no general spot price, historical pricing, or direct product comparison.

Available Tools

9 tools

check_availabilitySprawdź dostępność

Read-onlyIdempotent

Inspect

Status dostępności produktu (SKU): od ręki (wysyłka 24–48 h) / na zamówienie (7-10 dni) / skarbiec CH. Od ręki = WYSYŁKA w 24–48 h — nie mylić z 24-godzinnym terminem płatności. skarbiec_ch = wydanie tylko do skarbca Loomis (CH).

ParametersJSON Schema

Name	Required	Description	Default
`sku`	Yes
`waluta`	No

get_buyback_priceCena skupu (odkup)A

Read-onlyIdempotent

Inspect

Ceny SKUPU zlota i srebra — ile IDFMETALE ZAPLACI klientowi za posiadany kruszec. To NIE jest cena sprzedazy (od tego jest get_live_price ). Podaj metal, forme i mase sztuki, zeby dostac orientacyjna wycene; bez parametrow zwraca caly cennik skupu. Cena skupu jest ORIENTACYJNA i kubelkowa: zalezy od metalu, typu i gramatury, a NIE od mennicy — sztabka 100 g PAMP i 100 g Valcambi maja te sama cene skupu. Wiazaca wycena wymaga kontaktu z IDFMETALE i oceny stanu towaru. To NIE jest oferta w rozumieniu prawa. Dane mają charakter informacyjny i edukacyjny. NIE stanowią porady inwestycyjnej ani rekomendacji zakupu. IDFMETALE nie rokuje przyszłych cen ani zysków.

ParametersJSON Schema

Name	Required	Description
`forma`	No
`metal`	No
`masa_g`	No	masa jednej sztuki w gramach, np. 100 dla sztabki 100 g

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses important behaviors: the price is approximate and bucket-based, independent of mint, dependent only on metal/type/weight, and not a binding offer. It also provides legal and informational limitations, which is valuable context an agent should know before presenting results to a user.

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?

The description is front-loaded with the core purpose and then the key behavioral caveat, followed by legal disclaimers. The legal and disclaimer sentences add some length, but they are relevant for a financial pricing tool and do not obscure the operational content. Overall, it earns its place without excessive redundancy.

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?

For a tool with three optional parameters, clear annotations, and no output schema, the description is complete: it explains what the tool returns, how to invoke it with and without parameters, how the price model works, and what caveats apply. An agent has enough information to decide when and how to call it and what expectations to set with the user.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description must compensate, and it does: it explains that metal, form, and weight drive the estimate, clarifies that all parameters are optional with no-parameter behavior returning the full price list, and describes how weight/type affect pricing. It does not enumerate the exact enum options, but those are self-descriptive from the schema.

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 the specific purpose: it returns the buyback price IDFMETALE pays for gold or silver, and explicitly contrasts this with the sale price retrievable via get_live_price. It names the resource and the pricing perspective clearly, so an agent can distinguish it from sibling tools without inspecting the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage guidance: provide metal, form, and weight to get an estimated valuation, or call with no parameters to receive the full buyback price list. It also names the alternative tool get_live_price for sale prices and explains when the tool's result is not binding, making selection straightforward.

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

get_live_priceŻywa cena

Read-onlyIdempotent

Inspect

Aktualna cena produktu (SKU) w wybranej walucie: cena od (7-10 dni) i cena od ręki (wysyłka 24–48 h), jeśli na stanie, wraz ze znacznikiem ważności (cena_wazna_od/cena_wazna_do) i kosztem dostawy. Po cena_wazna_do cena jest NIEAKTUALNA — pobierz ją ponownie przed pokazaniem klientowi. Termin płatności 24h != gwarancja ceny.

ParametersJSON Schema

Name	Required	Description	Default
`sku`	Yes
`ilosc`	No
`waluta`	No

get_productSzczegóły produktu

Read-onlyIdempotent

Inspect

Pełne dane produktu po SKU lub handle: atrybuty (metal/forma/próba/masa/mennica/akredytacja), żywa cena od (7-10 dni) oraz cena od ręki (wysyłka 24–48 h), jeśli towar jest na stanie, dostępność, delivery_mode (skarbiec_ch = wydanie WYŁĄCZNIE do skarbca Loomis w CH, bez wysyłki/odbioru), status notowania, prawo odstąpienia (dla towaru notowanego wyłączone — art. 38), status VAT. Finalizacja zakupu wymaga weryfikacji KYC po stronie IDFMETALE (instytucja obowiązana AML). Agent nie finalizuje transakcji. Dane mają charakter informacyjny i edukacyjny. NIE stanowią porady inwestycyjnej ani rekomendacji zakupu. IDFMETALE nie rokuje przyszłych cen ani zysków.

ParametersJSON Schema

Name	Required	Description	Default
`ref`	Yes	SKU (np. ARG1) lub handle produktu
`waluta`	No

list_brandsLista mennic i akredytacjiA

Read-onlyIdempotent

Inspect

Zwraca listę mennic (producentów) oraz akredytacji (np. LBMA) obecnych w katalogu — rozdzielone.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds minor behavioral context by specifying that the result is separated into mints and accreditations, which does not contradict annotations.

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?

The description is a single sentence that is front-loaded and to the point. Every word is necessary, with no redundancy or fluff.

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 simple listing tool with no parameters and no output schema, the description adequately conveys what is returned (mints and accreditations, separated). However, it could additionally clarify the structure (e.g., two arrays) or mention if the list is paginated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, and the input schema coverage is 100%. The description adds no parameter details, but the baseline for 0 parameters is 4. No additional information is needed.

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 clearly states it returns a list of mints (producers) and accreditations (e.g., LBMA), using a specific verb ('Zwraca') and resource. It is distinct from sibling tools like list_categories or search_products, which have different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention context, exclusions, or prerequisites, leaving the agent to infer usage solely from the tool name and title.

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

list_categoriesLista kategoriiB

Read-onlyIdempotent

Inspect

Kategorie produktowe sklepu (handle + nazwa).

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, which fully describe the behavioral traits. The description adds minor context by mentioning the returned fields (handle + name), but does not significantly extend beyond the annotations.

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?

The description is a single sentence with no unnecessary words. It is front-loaded with the core purpose. However, it could be organized slightly better with more structured information, but it is sufficiently concise.

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?

Given the simplicity of the tool (no parameters, no output schema), the description is minimally adequate. It hints at output fields but does not specify ordering, pagination, or whether the list is exhaustive. For a simple list tool, this is acceptable but lacks some completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, and schema coverage is 100%. Baseline for zero parameters is 4. The description does not need to add parameter semantics, but it also does not provide any additional details about parameter behavior.

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 clearly states that the tool lists product categories and includes fields 'handle' and 'nazwa'. The verb 'list' and resource 'categories' are specific. It is distinct from sibling tools like 'list_brands' and 'search_products', but no explicit differentiation is provided.

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?

No guidance on when to use this tool versus alternatives. There are no prerequisites or context for when listing categories is appropriate. The description relies on the name and title to imply usage.

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

read_knowledgeFakty ze stron IDFA

Read-onlyIdempotent

Inspect

Treść publicznej strony IDF: dostawa, kontakt (adresy i godziny), jak kupić, ogólne zasady skupu. Dane źródłowe, nie instrukcje. Nie odpowiada na indywidualne sprawy, podatki ani AML.

ParametersJSON Schema

Name	Required	Description	Default
`page`	Yes	Slug strony (np. faq, platnosc, zloto-inwestycyjne) albo URL artykułu /pl/blog/ z search_knowledge. Pełna treść, bez stron konta i produktów.
`offset`	No

TDQS

A4/5.0

Behavior4/5

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

Annotations already signal read-only, idempotent, non-destructive behavior. The description adds useful behavioral boundaries: this is source material rather than guidance, and it deliberately does not answer individual, tax, or AML questions. It does not disclose output formatting or offset behavior, but the annotation coverage lowers the burden.

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?

The description is compact, front-loaded with the core content scope, and every sentence adds value. The list format and two short caveats are easy to parse and free of redundancy.

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 read-only retrieval tool, the description covers what content is returned and what the tool will not answer. No output schema exists, so a bit more return-format detail would help, and 'offset' semantics remain unexplained, but the overall picture is sufficient for basic correct invocation.

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?

The schema already documents the main 'page' parameter well, including slug/URL forms and exclusions. The description adds general topic context but does not clarify the 'offset' parameter, which is left undocumented at 50% schema coverage. No parameter information is repeated or contradicted.

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 clearly identifies the resource (public IDF page content) and lists specific content categories: delivery, contact, how to buy, and purchase rules. It avoids tautology, though it does not explicitly name sibling tools to differentiate itself from search_knowledge.

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 description gives clear scope and explicit exclusions: it provides source data, not instructions, and does not handle individual cases, taxes, or AML. It does not name alternative tools, but the exclusions are concrete enough to prevent common misuses.

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

search_knowledgeBaza wiedzy i poradniki

Read-onlyIdempotent

Inspect

Przewodniki, FAQ, slownik pojec i artykuly IDFMETALE o metalach inwestycyjnych: podatki i VAT, przechowywanie, odkup, mennice i akredytacja LBMA, oddzialy, jak kupic. Zwraca tytuly i adresy stron IDFMETALE — tresc czytaj pod linkiem. Dane mają charakter informacyjny i edukacyjny. NIE stanowią porady inwestycyjnej ani rekomendacji zakupu. IDFMETALE nie rokuje przyszłych cen ani zysków.

ParametersJSON Schema

Name	Required	Description
`typ`	No
`limit`	No
`query`	No	slowa kluczowe, np. »VAT srebro«, »odkup«, »przechowywanie«

search_productsSzukaj produktów

Read-onlyIdempotent

Inspect

Wyszukiwarka katalogu metali inwestycyjnych IDFMETALE. Filtruje po metalu, formie, próbie, mennicy, masie i zakresie ceny; zwraca ustrukturyzowane atrybuty + żywą cenę od i dostępność. Tylko produkty z kompletem danych. Wyniki sortowane rosnąco wg ceny (fakt, nie ranking). Finalizacja zakupu wymaga weryfikacji KYC po stronie IDFMETALE (instytucja obowiązana AML). Agent nie finalizuje transakcji. Dane mają charakter informacyjny i edukacyjny. NIE stanowią porady inwestycyjnej ani rekomendacji zakupu. IDFMETALE nie rokuje przyszłych cen ani zysków.

ParametersJSON Schema

Name	Required	Description
`forma`	No
`limit`	No
`metal`	No
`query`	No	filtr tekstowy po nazwie, SKU lub mennicy — zawężenie zbioru, NIE ranking trafności
`waluta`	No
`mennica`	No	np. Argor Heraeus, PAMP, Valcambi, C.Hafner, Perth Mint
`cena_max`	No	górny limit ceny 'od' w wybranej walucie
`dostepnosc`	No
`masa_g_max`	No
`masa_g_min`	No

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesOct 13, 2026
- Changedcheck_availability1 field changed
  - addedInput schema / properties / sku / maxLength
```
Added value: +64
```
- Changedget_live_price5 fields changed
  - addedInput schema / properties / ilosc / exclusiveMinimum
```
Added value: +0
```
  - addedInput schema / properties / ilosc / maximum
```
Added value: +10000
```
  - removedInput schema / properties / ilosc / minimum
```
Removed value: -1
```
  - changedInput schema / properties / ilosc / type
```
Previous value: -"number"New value: +"integer"
```
  - addedInput schema / properties / sku / maxLength
```
Added value: +64
```
- Changedget_product1 field changed
  - addedInput schema / properties / ref / maxLength
```
Added value: +64
```
- Changedsearch_knowledge1 field changed
  - addedInput schema / properties / query / maxLength
```
Added value: +128
```
- Changedsearch_products2 fields changed
  - addedInput schema / properties / mennica / maxLength
```
Added value: +64
```
  - addedInput schema / properties / query / maxLength
```
Added value: +128
```

1 tool updateSep 15, 2026

Changedread_knowledge4 fields changed

addedInput schema / properties / offset

Added value: +{
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / page / description

Added value: +"Slug strony (np. faq, platnosc, zloto-inwestycyjne) albo URL artykułu /pl/blog/ z search_knowledge. Pełna treść, bez stron konta i produktów."

removedInput schema / properties / page / enum

Removed value: -[
-  "kontakt",
-  "dostawa",
-  "jak-kupic",
-  "gwarancja-odkupu",
-  "skup",
-  "o-nas"
-]

addedInput schema / properties / page / maxLength
```
Added value: +300
```

1 tool updateSep 14, 2026
- Addedread_knowledge

3 tool updatesSep 5, 2026

Addedget_buyback_price
Addedsearch_knowledge

Changedsearch_products1 field changed

addedInput schema / properties / query

Added value: +{
+  "description": "filtr tekstowy po nazwie, SKU lub mennicy — zawężenie zbioru, NIE ranking trafności",
+  "type": "string"
+}

6 tool updatesJul 19, 2026
- First observedcheck_availability
- First observedget_live_price
- First observedget_product
- First observedlist_brands
- First observedlist_categories
- First observedsearch_products

Related MCP Connectors

troystack A
io.github.kingleosgold
Precious metals AI analyst with 12 tools — prices, portfolio, chat, receipts, and more.
Finance Search
122
Gold & Silver Company A
com.goldandsilvercompany
Official answers of Gold & Silver Company, precious metals refinery, Belgium (FR/EN/NL)
Customer Support
121
80% Silver Melt Calculator A
com.80percentsilver
Live junk silver and gold melt value calculator: spot price, coins, sterling. USD/CAD.
Finance
31
ZahabPrice — Live Gold & Silver Prices A
com.zahabprice
Live gold & silver prices for 37 countries. Tamara/Tabby installment calculators for Saudi Arabia.
Finance E-commerce & Retail
42

Related MCP Servers

cenogram-mcp-serverofficial
Government Data Real Estate
cenogram
A
license
A
quality
A
maintenance
7M+ real estate transactions from Poland's RCN registry. Search, compare, and analyze prices
Updated 21 days ago (2026-09-25 21:53 UTC)
28
77 npm
1
MIT
Poland
Government Data Legal & Compliance
Xopoko
A
license
Not graded
quality
A
maintenance
Your AI agent's practical guide to life and administration in Poland.
Updated a month ago (2026-09-05 12:35 UTC)
MIT
nipregon-mcp
Government Data Finance
AMR-DEV-PS
A
license
A
quality
C
maintenance
Look up Polish companies from any AI assistant: registry data (KRS, REGON, CEIDG), VAT white list checks before payments, and financial statements of 4.4M businesses. Read-only tools backed by official public registers.
Updated 4 months ago (2026-06-23 08:27 UTC)
4
MIT
@m8t-jacob/mcp-polish-biz
Government Data Finance Open Data
M8T-Jacob
A
license
A
quality
D
maintenance
MCP server that provides AI agents with Polish business data tools: identifier validation (NIP, PESEL, REGON, KRS, IBAN), VAT whitelist checks, EU VIES lookups, and NBP exchange rates.
Updated 3 months ago (2026-07-13 12:46 UTC)
5
8 npm
MIT