Skip to main content
Glama
Sign In

IDF Metale — gold & silver bullion (Poland)

by pl.idfmetale
OverviewDiscussionsAdmin

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 80 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Each tool targets a distinct resource: catalog search, single product, availability, live price, buyback price, brands, categories, and two knowledge tools. The descriptions actively guard against the main confusion (get_buyback_price vs get_live_price, check_availability vs 24h payment term), but get_product overlaps with both get_live_price and check_availability since it returns price and availability, and search_knowledge vs read_knowledge require reading carefully to tell apart (search returns links, read returns content).

Naming Consistency5/5

All nine names follow a strict verb_noun snake_case pattern (check_, get_, list_, read_, search_). Verbs map predictably to action type: get_ for single-entity fetch, list_ for enumerations, search_ for filtered discovery.

Tool Count5/5

Nine tools is well within a comfortable range and each maps to a real need in a bullion catalog server (product lookup, pricing, availability, taxonomy, documentation). No filler or vanity tools are present.

Completeness4/5

The read-only catalog surface is solid: search, single-product detail, live and buyback pricing, availability, brand/category taxonomy, and knowledge lookup. Minor gaps: list_categories returns handles that no tool actually consumes (no filter-by-category on search_products), and there is no multi-SKU price refresh or branch/delivery-cost lookup outside knowledge pages; order finalization is deliberately excluded via KYC, which is consistent with the stated scope.

Available Tools

9 tools
check_availabilitySprawdź dostępnośćB
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).

NameRequiredDescriptionDefault
skuYes
walutaNopln | eur | usd (wielkość liter dowolna: PLN, EUR, USD)

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real semantics beyond that: what each status means in fulfillment terms and that 'skarbiec_ch' restricts release to the Loomis vault (CH).

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?

Front-loaded with the status vocabulary the agent needs, and the warning about the shipping-vs-payment deadline earns its place as a real disambiguation. Phrasing is dense and slightly telegraphic but not padded.

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?

No output schema exists, and the description only partially fills that gap by naming the status values; it doesn't state the response shape or how the currency parameter affects the result. Adequate for a simple read-only lookup, but leaving gaps.

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

Parameters2/5

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

Schema coverage is only 50%: 'sku' has no schema description, and 'waluta' is documented only in the schema. The description mentions SKU only implicitly and says nothing about why a currency parameter matters for an availability check, so it does not compensate for the coverage gap.

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?

States a specific resource (product availability by SKU) and enumerates the exact status values it returns ('od ręki / na zamówienie / skarbiec CH'), so an agent knows precisely what it gets back. It does not, however, distinguish itself from siblings such as get_product, which might also surface stock state.

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?

Usage is implied (check stock state before ordering) and the description usefully disambiguates '24–48 h shipping' from the 24-hour payment deadline, but it never states when to call this versus get_product or when not to call it.

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

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.

NameRequiredDescriptionDefault
formaNoSztabka | Moneta (aliasy: bar, coin)
metalNoZłoto | Srebro (aliasy: gold/zloto, silver/srebro)
masa_gNomasa jednej sztuki w gramach, np. 100 dla sztabki 100 g

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), it discloses that prices are indicative and bucketed, depend on metal/type/weight but not on mint, and that a binding valuation requires contacting IDFMETALE. Useful, non-obvious behavior; the score is not 5 because a large share of the text is legal/educational boilerplate rather than tool behavior.

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?

The first three sentences are front-loaded and earn their place, but the closing disclaimer block is long, repetitive ('Dane mają charakter informacyjny...', 'NIE stanowią porady inwestycyjnej', 'nie rokuje przyszłych cen') and dilutes the operational content.

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 lookup with a complete schema and annotations, the description covers the essentials: no-parameter default, the bucketed/indicative nature of the price, and the non-binding caveat. It only marginally describes the returned price-list structure, which is acceptable given there is no output schema.

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 100% and the enums already document the accepted values, so baseline is 3. The description adds real meaning by framing the three optional parameters as filters for an estimate and by clarifying that no mint parameter exists because mint does not affect the quoted price.

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+resource: buyback ('SKUP') prices for gold and silver and the direction of payment (IDFMETALE pays the client). It explicitly distinguishes itself from get_live_price, so an agent can route correctly 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 Guidelines5/5

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

Gives explicit invocation guidance: pass metal, form and unit mass for an estimate, or omit all parameters to get the full buyback price list. It also names the alternative (get_live_price) and the condition that selects it (sale price), leaving nothing to inference.

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 cenaA
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.

NameRequiredDescriptionDefault
skuYes
iloscNo
walutaNopln | eur | usd (wielkość liter dowolna: PLN, EUR, USD)

TDQS

A3.9/5.0
Behavior4/5

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

Opis wnosi realną wartość ponad adnotacje (readOnly/idempotent/openWorld): ujawnia semantykę wygasania ceny przez znaczniki `cena_wazna_od`/`cena_wazna_do`, zależność wyniku od stanu magazynowego oraz to, że odpowiedź zawiera koszt dostawy. Nie opisuje natomiast zachowania przy braku SKU ani formatu błędów.

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?

Trzy zdania, wszystkie niosą informację: co zwraca, kiedy cena wygasa, jakie jest zastrzeżenie o terminie płatności. Gęste nawiasy i wtrącenia lekko utrudniają czytanie, ale nic nie jest zbędne.

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?

Brak output schema, więc opis musi udźwignąć kształt odpowiedzi — i robi to częściowo, wymieniając cztery zwracane pola (cena od, cena od ręki, znaczniki ważności, koszt dostawy). Nie wyjaśnia jednak struktury odpowiedzi ani zachowania przy nieistniejącym SKU.

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?

Pokrycie opisów w schemacie to 33% — tylko `waluta` ma opis, a enum i tak jest samowyjaśniający. Opis wyjaśnia sens `sku` i `waluta`, ale całkowicie pomija parametr `ilosc`, który najpewniej wpływa na próg cenowy; przy niskim pokryciu schematu to odczuwalna luka.

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?

Stany wyraźny czasownik i zasób: bieżąca cena produktu po SKU, z rozróżnieniem ceny 'od' (7-10 dni) i 'od ręki' (24-48 h). Wyraźnie odcina się od get_buyback_price przez wskazanie, że chodzi o cenę sprzedaży, ale nie wymienia po nazwie żadnego z narzędzi siostrzanych (np. check_availability przy warunku 'jeśli na stanie').

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?

Podaje konkretny warunek użycia i ponownego użycia: po `cena_wazna_do` cena jest NIEAKTUALNA i trzeba ją pobrać ponownie przed pokazaniem klientowi. Dodatkowo ostrzega, że termin płatności 24h nie jest gwarancją ceny. Brak jedynie jawnego wskazania alternatywy (np. 'stan magazynowy sprawdź przez check_availability').

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

get_productSzczegóły produktuA
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.

NameRequiredDescriptionDefault
refYesSKU (np. ARG1) lub handle produktu
walutaNopln | eur | usd (wielkość liter dowolna: PLN, EUR, USD)

TDQS

A3.6/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 still adds real domain behavior: KYC/AML verification is required to finalize a purchase, the agent must not finalize transactions, delivery_mode 'skarbiec_ch' means vault-only release with no shipping or pickup, and withdrawal rights are excluded for listed goods (art. 38). The only weakness is the closing block of legal boilerplate that restates disclaimers.

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?

The first sentence is dense and well front-loaded with the returned data set, but the paragraph then runs on into compliance/legal boilerplate, with several near-redundant sentences ('Dane mają charakter informacyjny...', 'NIE stanowią porady inwestycyjnej...', 'nie rokuje przyszłych cen'). The useful information is buried in a single unstructured block.

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 no output schema, the description carries the burden of explaining return content and does so thoroughly, enumerating attribute groups, the two price models with their lead times, availability, and delivery mode. Compliance context is also covered; only currency/price-timestamp semantics remain unaddressed.

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 100% and both parameters are documented in the schema, including the currency enum. The description only echoes the SKU-or-handle duality already present in the 'ref' parameter description and adds nothing about currency handling or price-day assumptions (7–10 days vs 24–48 h), so the baseline 3 applies.

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 opens with a specific verb and resource plus lookup key: 'Pełne dane produktu po SKU lub handle', then enumerates the returned domains (attributes, live price, spot price, availability, delivery_mode, listing status, withdrawal right, VAT status). This clearly separates it functionally from narrower siblings such as get_live_price or check_availability, though none of them is named explicitly.

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?

Usage is implied rather than stated: fetch full product detail by SKU/handle, and note that the agent does not finalize transactions. There is no explicit routing like 'use search_products to find a SKU first' or 'use get_live_price if you only need the price', so the agent must infer the boundary itself.

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

list_brandsLista mennic i akredytacjiA
Read-onlyIdempotent
Inspect

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

NameRequiredDescriptionDefault

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).

NameRequiredDescriptionDefault

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.

NameRequiredDescriptionDefault
pageYesSlug strony (np. faq, platnosc, zloto-inwestycyjne) albo URL artykułu /pl/blog/ z search_knowledge. Pełna treść, bez stron konta i produktów.
offsetNo

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 poradnikiA
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.

NameRequiredDescriptionDefault
typNoprzewodnik | blog | notowania | skup | producent | oddzial | prawne | firma | zakupy | katalog (aliasy EN: guide, article, prices, buyback, mint, branch, legal, company, shopping, catalog)
limitNo
queryNoslowa kluczowe, np. »VAT srebro«, »odkup«, »przechowywanie«

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds the return contract ('Zwraca tytuly i adresy stron') that the agent cannot see from any schema. The disclaimer block clarifies the informational scope of the data but is partly boilerplate legal text.

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?

The opening sentence is front-loaded and informative, but three of the five sentences are repetitive legal disclaimers ('informacyjny i edukacyjny', 'NIE stanowią porady', 'nie rokuje przyszłych cen'), which dilute rather than serve tool selection.

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 no output schema, the description correctly compensates by explaining that only titles and URLs are returned. Combined with read-only annotations and zero required parameters, an agent has enough to call it correctly; the missing piece is an explicit pointer to read_knowledge for fetching page content.

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 67%: the 'typ' enum and 'query' already carry inline examples and aliases, while 'limit' is undocumented in both places. The description adds no additional parameter meaning (no guidance on combining query with typ or on default limit), so baseline 3 applies.

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 a specific resource set (przewodniki, FAQ, słownik pojęć, artykuły) scoped to investment metals and states the return shape (titles and page URLs). It implicitly separates itself from a content-reading tool by saying 'tresc czytaj pod linkiem', though it never names read_knowledge explicitly.

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?

Usage is only implied: the phrase 'tresc czytaj pod linkiem' hints that this is a discovery step before reading a full page. There is no explicit statement of when to pick this over read_knowledge or search_products, and no exclusion of product/price lookups that the sibling tools cover.

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

search_productsSzukaj produktówA
Read-onlyIdempotent
Inspect

Wyszukiwarka katalogu metali inwestycyjnych IDFMETALE. Filtruje po metalu, formie, próbie, mennicy, masie, dostępności i zakresie ceny; zwraca ustrukturyzowane atrybuty, żywą cenę od (na zamówienie, 7-10 dni) oraz cenę od ręki cena_24h (wysyłka 24–48 h) dla towaru na stanie — te same kwoty co get_live_price. Enumy przyjmują wartości polskie i angielskie aliasy (np. metal: "gold" = "Złoto"). Produkty bez kompletu atrybutów nie trafiają do produkty, ale są wymienione z nazwy w pominiete_bez_danych. Pole query rozumie wagę ("1 oz", "1/10 oz", "1/4 uncji", "31,1 g", "100 g", "1 kg"; filtr masy ±2 %), metal i formę po polsku i angielsku (gold/silver, bar/coin) oraz angielskie nazwy monet (Maple Leaf, Eagle, Philharmonic, Kangaroo/Nugget, Sovereign…); liczby dopasowuje jako całe tokeny ("100 g" nie trafia w "1/100 oz"); interpretację zwraca w interpretacja_zapytania. Bez query wyniki sortowane rosnąco wg ceny (fakt, nie ranking); z query — wg zgodności z zapytaniem (nazwa > waga > metal), potem wg ceny. Towar sprzedawany na jednostki (sztaba srebra 1000 oz) ma cenę za uncję, masę i wartość minimalnego zamówienia (cena_calkowita_min). 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.

NameRequiredDescriptionDefault
formaNoSztabka | Moneta | Moneta Kolekcjonerska. Aliasy: bar, coin, collectible_coin
limitNo
metalNoZłoto | Srebro | Srebro VAT | Platyna | Pallad. Aliasy: gold/zloto, silver/srebro, silver_vat, platinum/platyna, palladium/pallad. Srebro = srebro z VAT-marżą, Srebro VAT = srebro z pełnym VAT 23 % — to DWIE osobne wartości; całe srebro: pomiń `metal` i podaj query "srebr".
queryNoTekst po polsku lub angielsku: nazwa/SKU/mennica + waga ("1 oz", "1/10 oz", "1/4 uncji", "31,1 g", "100 g", "1 kg" → filtr masy ±2 %), metal (złoto/gold, srebro/silver) i forma (sztabka/bar, moneta/coin). Przykłady: "Krugerrand 1/10 oz", "gold bar 1 oz", "Maple Leaf 1 oz", "sztabka złota 100 g", "KRUG110". Słowa ogólne i spoza katalogu są pomijane i wymienione w `interpretacja_zapytania`; gdy dokładnego dopasowania brak, wynik jest przybliżony (`dopasowanie`, `pominiete_warunki_zapytania`).
walutaNopln | eur | usd (wielkość liter dowolna: PLN, EUR, USD)
mennicaNonp. Argor Heraeus, PAMP, Valcambi, C.Hafner, Perth Mint
cena_maxNogórny limit ceny 'od' (tryb na zamówienie) w wybranej walucie
dostepnoscNood_reki (wysyłka 24–48 h) | na_zamowienie (7-10 dni). Aliasy: in_stock, on_order
masa_g_maxNo
masa_g_minNo

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that KYC verification is required for purchase finalization and that the agent never completes transactions, that incomplete products appear only in `pominiete_bez_danych`, that query interpretation is echoed in `interpretacja_zapytania`, and that unit-sold items carry per-ounce pricing with a minimum order value. Annotations already cover read-only/idempotent safety, so this is substantial added context.

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?

Front-loaded with purpose, but it is a single dense block that repeats query-parsing details already present in the `query` schema field. Three trailing sentences of legal/educational disclaimer boilerplate ('nie stanowią porady inwestycyjnej', 'nie rokuje przyszłych cen') consume space without helping an agent select or invoke the tool.

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 10 parameters and no output schema, the description carries return-shape information well (`produkty`, `pominiete_bez_danych`, `interpretacja_zapytania`, `cena_24h`, `cena_calkowita_min`) and explains sort order. The gaps are pagination and the role of `limit`, which are not covered anywhere.

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 70%, and the description meaningfully extends it, especially for `query`: weight parsing with ±2% tolerance, whole-token matching ('100 g' not matching '1/100 oz'), Polish/English aliases and coin names. It leaves `limit` and `masa_g_min`/`masa_g_max` unaddressed, and the Srebro vs Srebro VAT distinction is already in 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?

Opens with a specific verb+resource: a catalog search over IDFMETALE investment metals, enumerating the filterable facets (metal, form, purity, mint, weight, availability, price range). It partially differentiates from siblings by noting the returned amounts match get_live_price, though it never contrasts itself with get_product or check_availability.

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?

Usage is implied rather than stated: the description explains sorting differences with and without `query` and notes that products missing attributes are excluded, which hints at how to query. But there is no explicit 'use this instead of X when Y' guidance against the eight sibling tools, and no stated exclusions.

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

Tool Schema Changelog

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

  1. 1 tool update
    • Changedsearch_products1 field changed
      • changedInput schema / properties / query / description
        Previous value: -"filtr tekstowy po nazwie, SKU lub mennicy — zawężenie zbioru, NIE ranking trafności"New value: +"Tekst po polsku lub angielsku: nazwa/SKU/mennica + waga (\"1 oz\", \"1/10 oz\", \"1/4 uncji\", \"31,1 g\", \"100 g\", \"1 kg\" → filtr masy ±2 %), metal (złoto/gold, srebro/silver) i forma (sztabka/bar, moneta/coin). Przykłady: \"Krugerrand 1/10 oz\", \"gold bar 1 oz\", \"Maple Leaf 1 oz\", \"sztabka złota 100 g\", \"KRUG110\". Słowa ogólne i spoza katalogu są pomijane i wymienione w `interpretacja_zapytania`; gdy dokładnego dopasowania brak, wynik jest przybliżony (`dopasowanie`, `pominiete_warunki_zapytania`)."
  2. 6 tool updates
    • Changedcheck_availability2 fields changed
      • addedInput schema / properties / waluta / description
        Added value: +"pln | eur | usd (wielkość liter dowolna: PLN, EUR, USD)"
      • changedInput schema / properties / waluta / enum
        Previous value: -[
-  "pln",
-  "eur",
-  "usd"
-]New value: +[
+  "pln",
+  "PLN",
+  "eur",
+  "EUR",
+  "usd",
+  "USD"
+]
    • Changedget_buyback_price4 fields changed
      • addedInput schema / properties / forma / description
        Added value: +"Sztabka | Moneta (aliasy: bar, coin)"
      • changedInput schema / properties / forma / enum
        Previous value: -[
-  "Sztabka",
-  "Moneta"
-]New value: +[
+  "Sztabka",
+  "sztabka",
+  "bar",
+  "Bar",
+  "Moneta",
+  "moneta",
+  "coin",
+  "Coin"
+]
      • addedInput schema / properties / metal / description
        Added value: +"Złoto | Srebro (aliasy: gold/zloto, silver/srebro)"
      • changedInput schema / properties / metal / enum
        Previous value: -[
-  "Złoto",
-  "Srebro"
-]New value: +[
+  "Złoto",
+  "złoto",
+  "zloto",
+  "Zloto",
+  "gold",
+  "Gold",
+  "Srebro",
+  "srebro",
+  "silver",
+  "Silver"
+]
    • Changedget_live_price2 fields changed
      • addedInput schema / properties / waluta / description
        Added value: +"pln | eur | usd (wielkość liter dowolna: PLN, EUR, USD)"
      • changedInput schema / properties / waluta / enum
        Previous value: -[
-  "pln",
-  "eur",
-  "usd"
-]New value: +[
+  "pln",
+  "PLN",
+  "eur",
+  "EUR",
+  "usd",
+  "USD"
+]
    • Changedget_product2 fields changed
      • addedInput schema / properties / waluta / description
        Added value: +"pln | eur | usd (wielkość liter dowolna: PLN, EUR, USD)"
      • changedInput schema / properties / waluta / enum
        Previous value: -[
-  "pln",
-  "eur",
-  "usd"
-]New value: +[
+  "pln",
+  "PLN",
+  "eur",
+  "EUR",
+  "usd",
+  "USD"
+]
    • Changedsearch_knowledge2 fields changed
      • addedInput schema / properties / typ / description
        Added value: +"przewodnik | blog | notowania | skup | producent | oddzial | prawne | firma | zakupy | katalog (aliasy EN: guide, article, prices, buyback, mint, branch, legal, company, shopping, catalog)"
      • changedInput schema / properties / typ / enum
        Previous value: -[
-  "przewodnik",
-  "blog",
-  "notowania",
-  "skup",
-  "producent",
-  "oddzial",
-  "prawne",
-  "firma",
-  "zakupy",
-  "katalog"
-]New value: +[
+  "przewodnik",
+  "guide",
+  "blog",
+  "article",
+  "notowania",
+  "prices",
+  "quotes",
+  "skup",
+  "buyback",
+  "producent",
+  "mint",
+  "producer",
+  "oddzial",
+  "branch",
+  "prawne",
+  "legal",
+  "firma",
+  "company",
+  "zakupy",
+  "shopping",
+  "how_to_buy",
+  "katalog",
+  "catalog",
+  "catalogue"
+]
    • Changedsearch_products9 fields changed
      • changedInput schema / properties / cena_max / description
        Previous value: -"górny limit ceny 'od' w wybranej walucie"New value: +"górny limit ceny 'od' (tryb na zamówienie) w wybranej walucie"
      • addedInput schema / properties / dostepnosc / description
        Added value: +"od_reki (wysyłka 24–48 h) | na_zamowienie (7-10 dni). Aliasy: in_stock, on_order"
      • changedInput schema / properties / dostepnosc / enum
        Previous value: -[
-  "od_reki",
-  "na_zamowienie"
-]New value: +[
+  "od_reki",
+  "in_stock",
+  "ready_to_ship",
+  "na_zamowienie",
+  "on_order",
+  "made_to_order"
+]
      • addedInput schema / properties / forma / description
        Added value: +"Sztabka | Moneta | Moneta Kolekcjonerska. Aliasy: bar, coin, collectible_coin"
      • changedInput schema / properties / forma / enum
        Previous value: -[
-  "Sztabka",
-  "Moneta",
-  "Moneta Kolekcjonerska"
-]New value: +[
+  "Sztabka",
+  "sztabka",
+  "bar",
+  "Bar",
+  "Moneta",
+  "moneta",
+  "coin",
+  "Coin",
+  "Moneta Kolekcjonerska",
+  "moneta kolekcjonerska",
+  "moneta_kolekcjonerska",
+  "collectible_coin",
+  "collectible coin"
+]
      • addedInput schema / properties / metal / description
        Added value: +"Złoto | Srebro | Srebro VAT | Platyna | Pallad. Aliasy: gold/zloto, silver/srebro, silver_vat, platinum/platyna, palladium/pallad. Srebro = srebro z VAT-marżą, Srebro VAT = srebro z pełnym VAT 23 % — to DWIE osobne wartości; całe srebro: pomiń `metal` i podaj query \"srebr\"."
      • changedInput schema / properties / metal / enum
        Previous value: -[
-  "Złoto",
-  "Srebro",
-  "Srebro VAT",
-  "Platyna",
-  "Pallad"
-]New value: +[
+  "Złoto",
+  "złoto",
+  "zloto",
+  "Zloto",
+  "gold",
+  "Gold",
+  "Srebro",
+  "srebro",
+  "silver",
+  "Silver",
+  "Srebro VAT",
+  "srebro vat",
+  "srebro_vat",
+  "silver_vat",
+  "silver vat",
+  "Platyna",
+  "platyna",
+  "platinum",
+  "Platinum",
+  "Pallad",
+  "pallad",
+  "palladium",
+  "Palladium"
+]
      • addedInput schema / properties / waluta / description
        Added value: +"pln | eur | usd (wielkość liter dowolna: PLN, EUR, USD)"
      • changedInput schema / properties / waluta / enum
        Previous value: -[
-  "pln",
-  "eur",
-  "usd"
-]New value: +[
+  "pln",
+  "PLN",
+  "eur",
+  "EUR",
+  "usd",
+  "USD"
+]
  3. 5 tool updates
    • 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
  4. 1 tool update
    • 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
  5. 1 tool update
    • Addedread_knowledge
  6. 3 tool updates
    • 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"
+}
  7. 6 tool updates
    • First observedcheck_availability
    • First observedget_live_price
    • First observedget_product
    • First observedlist_brands
    • First observedlist_categories
    • First observedsearch_products

Related MCP Connectors

Related MCP Servers

  • TroyStack API

    kingleosgold
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables access to live precious metals prices, historical data, market intelligence, and portfolio management with AI/LLM integration.
    ISC

  • ReserveOracle

    ToolOracle
    A
    license
    Not graded
    quality
    C
    maintenance
    Reserve Asset Intelligence MCP — live gold/silver prices as ES256K-signed evidence payloads, 80+ RWA token profiles (PAXG, XAUT, BlackRock BUIDL) with issuer LEI, custody, MiCA Art.36 context, and real cryptographic signatures.
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources