Skip to main content
Glama

Podziemie Analityczne

Related series

podziemie_related_series
Read-onlyIdempotent

The accepted, current links stored for a series, the record its page takes its links from: formula inputs, components, price-chain steps, publisher-stated mechanisms and reviewed "see also" series, each with its kind, tier, basis and direction. Navigation hints, not proof of a cause.

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

Input Schema

NameRequiredDescriptionDefault
idNoPublic series id: a slug or <dataset>/<dimension>=<code>.
slugNoSeries id, e.g. "inflacja-cpi" (from podziemie_search_series).
kindsNoOnly links of these kinds; default every kind.
tiersNocore: a formula, component, price-chain step or publisher-stated mechanism; worth_seeing: a reviewed "see also" pointer, never a cause. Default both.

Output Schema

NameRequiredDescriptionDefault
idNo
nameNo
slugYes
itemsNo
caveatNo
statusYes
suggestionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Annotations already carry readOnly, idempotent, closed-world and non-destructive, so the safety profile needs no restating. The description nonetheless adds real context beyond them: it says the links are 'accepted, current' ones (implying pending or rejected links are excluded) and warns that these are 'navigation hints, not proof of a cause'. That epistemic caveat is exactly the kind of guidance annotations cannot encode.

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 description is short overall, but it is a single convoluted sentence whose middle clause ('the record its page takes its links from') is hard to parse and pushes the useful caveat to the very end. The final warning sentence is well-placed and earns its space, but the front-loading of the main clause is weak.

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?

With an output schema, full param coverage, and annotations, the description covers enough to call the tool competently. Still missing is the sibling boundary (notably versus podziemie_get_neighbours) and any indication of behaviour when a series has no qualifying links, which matters for an agent deciding between the two neighbour-style tools.

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 id/slug and defines the kind and tier enums, giving a baseline of 3. The description's enumeration of link kinds and its note that 'see also' series are never a cause reinforces the meaning of the worth_seeing tier, but it does not add format, precedence, or defaulting information beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (links stored for a series) and enumerates the link categories (formula inputs, components, price-chain steps, publisher-stated mechanisms, 'see also'), which lets an agent grasp what comes back. However, the core clause 'the record its page takes its links from' is grammatically garbled and never states a clean verb, and there is no differentiation from the closely named sibling podziemie_get_neighbours, which an agent would plausibly confuse with this tool.

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?

There is no explicit statement of when to call this versus podziemie_get_neighbours, podziemie_get_series, or podziemie_describe_series, and no prerequisites such as needing a slug from podziemie_search_series. Usage can only be inferred from the resource type, and the most obvious alternative (get_neighbours) is left completely unaddressed.

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