Skip to main content
Glama

Podziemie Analityczne

Find members

podziemie_find_members
Read-onlyIdempotent

Find the code of a place or country by name or code in the shared code lists, with its level and parent: geography takes a Polish voivodeship name or TERYT code and, once places launch, a powiat, gmina (TERC) or village (SIMC) name or code, a village with its gmina and an abolished unit with its end date (podziemie_get_place reads their values); country takes a Polish or English name or an ISO 3166-1 alpha-2 or alpha-3 code (the Eurostat codes UK and EL also work); with dataset, the series ids for the other tools. Several fitting names come back as ambiguous.

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": {
      "dimension": "<dimension>"
    },
    "name": "podziemie_find_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoOnly members of this level; village is a member with no level of its own.
limitNoAt most this many members (default 20, at most 50).
queryNoA name or code, with or without Polish diacritics: geography by Polish name or TERYT code ("Mazowieckie", "14"; once places launch also "bocheński", "Nowy Wiśnicz", "1201063" or a village name); country by Polish or English name or ISO 3166-1 alpha-2 or alpha-3 code ("Niemcy", "Germany", "DE", "DEU"; "UK" and "EL" are Eurostat codes, ISO has GB and GR). Omit to list.
datasetNoA dataset id, e.g. "bezrobocie-wojewodztwa": only its members, each with its series id.
dimensionYesShared dimension: geography holds TERYT codes, country ISO 3166-1 alpha-2 codes and publisher area aggregates.
containedInNoA TERYT code: only members inside it, e.g. "12" for the members inside Małopolskie.

Output Schema

NameRequiredDescriptionDefault
hintNo
totalYes
statusYes
membersYes
dimensionYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 closed-world, so the safety profile is covered. The description still adds real behavioral value by warning that 'several fitting names come back as ambiguous' and by noting forward-looking support for powiat/gmina/village names and abolished units with an end date.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entire description is a single ~130-word run-on sentence with semicolons and nested parentheticals, which makes it hard to parse. The core purpose is front-loaded, but most of the middle is geographic edge-case exposition that could be bulleted or trimmed.

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?

An output schema exists, so return values need not be explained, and the one required parameter is well covered in the description. What is missing is any coverage of the many non-geographic dimensions (sex, age, sector, currency, product, etc.) that the schema exposes, leaving the description narrower than the 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 the schema already documents every parameter and the examples for query, level, dimension and containedIn. The description restates the same name/code rules almost verbatim and only mildly extends meaning by implying dataset lookups return series ids. Baseline 3 is appropriate.

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 opening clause states a specific verb and resource: find the code of a place or country by name/code in the shared code lists, returning level and parent. It distinguishes itself reasonably from podziemie_get_place (which reads the underlying values). However, it frames the tool almost entirely around geography and country while the schema shows 14 supported dimensions, so an agent may not realize it is a general dimension-member lookup.

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?

Useful context is implied rather than stated: 'omit to list', 'with dataset, the series ids for the other tools', and the pointer to podziemie_get_place for reading values. There is no explicit when-to-use/when-not framing, and no comparison against siblings like podziemie_search_series for non-code lookups, so the agent must infer routing.

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