Skip to main content
Glama

Series, person or year

get_catalog_entity
Read-only

Explain a coin series, a credited artist or sculptor, or a catalogue year, and list its coins. Covers «coins of the series X», «coins by the artist X» and «coins of 2024», and returns series and person ids.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_type": "<entity_type>"
    },
    "name": "get_catalog_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe entity id (for a year, the year itself). Give id or name, not both.
nameNoA name or part of it, in Ukrainian, when the id is not known. Not for a year.
cursorNonext_cursor of the previous page, with the same other arguments.
page_sizeNoCoins per page.
entity_typeYesseries = a coin series; person = an artist or sculptor credited on coins; year = a catalogue year.

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 covered. The description adds only that series and person ids are returned (useful for chaining calls); it says nothing about pagination behavior, ordering, or empty-result handling beyond what the schema and output schema already convey.

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 tight sentences: the first front-loads the capability and scope, the second supplies the query patterns and return shape. There is no filler and nothing that merely repeats the title.

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 and full schema coverage, the description need not explain return values or paging, and it correctly covers the three entity types. The only minor gap is that it does not note the id/name exclusivity or the year-specific id convention at the description level, though the schema handles both.

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 five parameters—including the entity_type enum and the 'give id or name, not both' rule—are already documented in the schema. The description adds no format or syntax detail for id/name/cursor beyond restating the entity kinds, which matches the baseline of 3 when the schema does the heavy lifting.

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 gives a specific verb and three concrete resources ('Explain a coin series, a credited artist or sculptor, or a catalogue year, and list its coins'), which maps exactly to the entity_type enum. It also supplies natural-language query exemplars, so an agent can tell this apart from search_coins or get_coin_details without inspecting schemas.

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 three quoted phrasings («coins of the series X», «coins by the artist X», «coins of 2024») make the triggering context clear, and the mention of returning series/person ids hints at follow-up use. It stops short of naming an alternative tool or an explicit when-not-to-use case, so it is clear context rather than full routing guidance.

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