subjectsBrowse the Kosovo Agency of Statistics (ASKdata) PxWeb subject tree. Default path 'ASKdata' returns top-level folders (type 'l') and tables (type 't', '.px' suffix). Supply a deeper sub-path like 'ASKdata/Prices/Consumer Price Index' to drill into a subject area.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Sub-path (default "ASKdata" = top database). e.g. "ASKdata/Prices/Consumer Price Index". |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "path": "ASKdata"
+ },
+ {
+ "path": "ASKdata/Prices/Consumer Price Index"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and open-world hints. The description adds value by detailing return types ('l' and 't' folders/tables) and path behavior, going beyond structured metadata.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, each carrying essential information. No redundant phrasing. Front-loaded with purpose followed by usage instructions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a single parameter, thorough annotations, and no output schema, the description adequately explains input behavior and expected output types. It could elaborate on the exact structure of returned items, but the provided details are sufficient for a browse tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a clear description. The description adds context by explaining the default value and providing real-world path examples, which enhances the schema's documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool browses the ASKdata subject tree, specifies default path behavior, and demonstrates drill-down capability. It distinguishes itself from sibling tools by its focus on hierarchical subject navigation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear usage examples (default and deeper paths) but does not explicitly mention when to avoid this tool or suggest alternatives. It gives enough context for appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.