Skip to main content
Glama

Veseljko katalog usluga za proslave

Prigode (occasions)

list_occasions
Read-onlyIdempotent

Lists the occasions businesses can be filtered by (vjenčanje, krštenje, rođendan, dječji rođendan, pričest, krizma, poslovni događaj...) with their keys and page counts. Use an occasion key as "occasion" in search_businesses.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond them by disclosing what the call returns — occasion keys plus page counts — which matters since there is no output schema. It does not say whether the list is static or reflects current data, a minor remaining gap.

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?

Two sentences, both earning their place: the first defines the resource and return shape, the second tells the agent what to do with the result. The parenthetical value list is long but functionally useful for matching a user's term to this tool rather than a sibling.

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?

For a zero-parameter lookup with no output schema, the definition covers purpose, return contents, and downstream usage, which is close to everything an agent needs. Only the freshness/staticness of the list and whether counts are totals or per-page remain 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?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline applies. The description correctly spends no space on inputs and instead explains how the output feeds another tool's parameter.

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 and resource ("Lists the occasions businesses can be filtered by") and adds the return contents (keys and page counts). The parenthetical examples of actual occasion values (vjenčanje, krštenje, rođendan...) make the resource unambiguous versus list_categories or list_places.

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 routes the agent forward: "Use an occasion key as 'occasion' in search_businesses." That is clear when-to-use guidance tied to a named sibling. It does not state when this lookup is unnecessary (e.g., if the key is already known), so it falls short of a full 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