Skip to main content
Glama

Search the MONETEKA catalogue

search_coins
Read-only

Search MONETEKA's catalogue of Ukrainian coins and banknotes by name and facets. Each result carries the coin_id the other coin tools take.

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": "search_coins"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNocoin = commemorative coin, circulating = circulating coin, bullion = investment coin, banknote, souvenir, set, roll.
sortNodate = newest first (best matches first when a query is given); name = alphabetical.date
yearNoCatalogue year of the item.
queryNoWords from the name, series or description, in Ukrainian; a nominal with a year works too («2 гривні 1996»).
cursorNonext_cursor of the previous page, with the same other arguments.
page_sizeNoItems per page.
person_idNoid of a person from get_catalog_entity; only coins that credit this artist or sculptor.
series_idNoid of a series from get_catalog_entity; only coins of that series.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is carried by structured data rather than the text. The description adds one genuinely useful behavioral fact — that each result carries a coin_id for chaining — but says nothing about result set size, ordering behavior, or empty-result handling, which the schema only partially covers via sort/cursor.

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?

Two sentences, both front-loaded with the highest-value information: what is searched first, the coin_id handoff second. No redundant restatement of the name, no filler.

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 unnecessary, and all eight parameters are schema-documented. What is missing is minor but real: no note on how to page through large catalogue results or what a zero-match search returns, and no mention that query text must be Ukrainian outside the schema. Adequate for a zero-required-parameter search tool.

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%, so all eight parameters (kind, sort, year, query, cursor, page_size, person_id, series_id) are already documented, including the Ukrainian-language query hint and the "same other arguments" rule for cursor. The description adds only the loose phrase "by name and facets," which does no work beyond the schema. Baseline 3 is appropriate.

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 (search) plus a precise resource and scope: "MONETEKA's catalogue of Ukrainian coins and banknotes by name and facets." The second sentence adds the distinguishing output hook — results carry the coin_id that other coin tools consume — so an agent can tell this apart from get_catalog_entity or get_coin_details.

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?

Implies the usage context clearly (name/facet discovery over the catalogue) and explains the downstream handoff to "the other coin tools" via coin_id. It stops short of naming an explicit alternative such as get_coin_details for when an id is already known, or when to prefer get_catalog_entity, so the when-not case is left to inference.

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.

Resources