Skip to main content
Glama

Veseljko katalog usluga za proslave

Mjesta (counties, regions, towns)

list_places
Read-onlyIdempotent

Lists the Croatian counties (županije), regions (Dalmacija, Istra, Kvarner, Slavonija...) and towns that have public pages, with their keys and page counts. Use a county or region key as "county" and a town key as "town" in search_businesses. Businesses that work all over Croatia count for every place.

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

Input Schema

NameRequiredDescriptionDefault
countyNoA county key (for example "splitsko-dalmatinska"): only its towns are listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral context: only places with public pages are included, and nationwide businesses are counted for every place, which explains otherwise surprising page counts. It does not describe pagination or whether all levels come back in a single flat list, so the added value is moderate.

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?

Three compact sentences, front-loaded with what is listed and what each row carries, followed by routing guidance and one count-semantics caveat. Every sentence carries distinct information with no restatement of the name or 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 no output schema, the description must explain return values, and it does: keys plus page counts per place. Combined with the zero-required-parameter schema and rich annotations, this is nearly complete; only the shape of the returned list (flat vs grouped by level) is left unstated.

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% and the schema already says the county param restricts output to that county's towns. The description contributes beyond that by stating that region keys (not just county keys) are also accepted in the "county" parameter, a semantic the schema does not mention given maxLength 80 with no enum.

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?

States a specific verb (lists) and a precisely scoped resource: Croatian counties, regions and towns that have public pages, plus what comes back (keys and page counts). An agent can immediately tell this is the place-taxonomy lookup rather than a business search, and the named levels (županije, Dalmacija/Istra/Kvarner/Slavonija, towns) leave no ambiguity about granularity.

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?

Explicitly tells the agent how to consume the output: use a county or region key as "county" and a town key as "town" in search_businesses, which effectively frames this as the prerequisite step before a business search. It stops short of an explicit when-not-to-use clause or naming list_categories/list_occasions as alternatives, so a 4 rather than a 5.

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