Skip to main content
Glama

Podziemie Analityczne

Poznaj Polskę

podziemie_poznaj
Read-onlyIdempotent

The site's profile of Poland (Poznaj Polskę) as one tree: twelve segments (population, work, prices, the economy, regions and more), each with its headline's latest reading and the page it leads to. A segment with its own page adds its year range, the series and table ids its charts draw, its facts and its links. The same tree as GET /api/poznaj.

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_poznaj"
  }
}

Input Schema

NameRequiredDescriptionDefault
segmentNoOne segment by its id; default every segment.

Output Schema

NameRequiredDescriptionDefault
urlNo
schemaNo
statusYes
segmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world call. The description adds useful behavior beyond that: the return is a tree of twelve segments, each carries its latest headline reading and target page, and detailed segments include year ranges, series/table ids, facts, and links. This gives the agent a meaningful preview of the result structure without restating annotation flags.

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 dense but front-loaded: it identifies the resource, enumerates what the tree contains, then explains segment-level enrichment. The GET endpoint mapping is compact and useful; little is wasted, though the sentence is long and could be split for readability.

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?

The tool has an output schema and full annotations, so the description need not explain every return field. It is complete enough for an agent to know this is an overview-tree call, what the optional segment does, and what extra content appears for segments with their own pages.

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%, so the enum and optional nature of segment are already documented. The description adds context by explaining that selecting a segment with its own page yields extra year ranges, series/table ids, facts, and links, which helps an agent understand what the parameter changes in the returned tree.

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 states a specific resource and shape: the site's profile of Poland returned as one tree with twelve named segments. It is clear enough to distinguish from sibling series- and observation-level tools by being an overview tree, although it does not explicitly name an alternative.

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: an agent can infer this is a discovery/overview call because it returns headline readings and links to segment pages. There is no explicit when-to-use guidance, no when-not-to-use guidance, and no named sibling alternative.

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