Skip to main content
Glama

Veseljko katalog usluga za proslave

Pretraži katalog (search)

search_businesses
Read-onlyIdempotent

Searches the catalogue's public pages, 24 per page, ranked the way the catalogue on veseljko.hr ranks them. Combine filters (category, group, county, town, occasion, guests) with Croatian search words in "query": the words are read for kinds, places, occasions and guest counts ("fotograf vjenčanje Split", "sala za 150 gostiju", "torta za rođendan Zagreb") and matched by meaning too. Write the words in Croatian; translate the user's request first. Every argument is optional: none lists everything. Returns each page's id, name, category, town, short description, capacity, occasions, badges and address; call get_business with an id for the full page. For the next page, call again with page + 1 and the same seed, so the order stays the same.

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

Input Schema

NameRequiredDescriptionDefault
pageNoThe page of results, from 1.
seedNoThe seed a previous call returned, to keep the same order when paging.
townNoA town key from list_places (e.g. "split", "zagreb", "rovinj").
groupNoOnly venues (prostor), event planners (organizator) or other services (partner).
queryNoCroatian search words, e.g. "bend za vjenčanje", "fotograf Split", "sala za 150 gostiju".
countyNoA county or region key from list_places (e.g. "istarska", "dalmacija").
guestsNoHow many guests: venues that seat at least about this many.
categoryNoA category key from list_categories (e.g. "fotograf", "bend", "sala", "katering").
occasionNoAn occasion key from list_occasions (e.g. "vjencanje", "krstenje", "rodendan").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds real operational context beyond that: page size of 24, catalogue-specific ranking, semantic matching of Croatian words, and seed-stable ordering. It does not, however, discuss rate limits or empty-result behavior, so it is solid but not exhaustive.

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?

Front-loaded with scope and ranking, then filters, then return values, then paging — a logical order. It is dense with parenthetical examples and has minor redundancy between the filter list and 'Every argument is optional', but each sentence carries operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, zero-required search tool with no output schema, the description covers page size, ranking, filter semantics, language requirements, all-optional behavior, returned fields, and continuation strategy. An agent has everything needed to call it correctly and to page through results.

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 baseline is 3, but the description adds meaning the schema cannot: the query must be written in Croatian and translated from the user's request, and it is parsed for kinds, places, occasions and guest counts. It also explains the seed/page relationship that keeps ordering stable, which the schema only hints at.

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?

Opens with a specific verb and resource plus scope: 'Searches the catalogue's public pages, 24 per page, ranked the way the catalogue on veseljko.hr ranks them.' It also implicitly separates itself from siblings by pointing to get_business for full records and list_* keys for filter values.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states how to combine filters with the query, that every argument is optional and an empty call lists everything, and routes the agent onward: 'call get_business with an id for the full page.' It also gives the exact paging procedure ('page + 1 and the same seed'), leaving nothing to inference.

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