Skip to main content
Glama

Veseljko katalog usluga za proslave

Stranica tvrtke (one business)

get_business
Read-onlyIdempotent

Returns one public page in full: description, services, occasions, place and the counties it also works in, capacity and halls, price list when the business shows it, contacts, how to send an inquiry, pictures, and for venues the floor plans (tlocrt) they publish. Give the id from search_businesses ("fotograf/studio-lunar") or the page's address on veseljko.hr.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe page's id from search_businesses: "category/slug", e.g. "fotograf/studio-lunar".
urlNoOr the page's address, e.g. "https://veseljko.hr/fotograf/studio-lunar".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavior context beyond that: it returns public page data, the price list appears only when the business publishes it, and floor plans exist only for venues, so the agent knows some fields may be absent.

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 the outcome, then a long but efficient inventory of returned content, then the argument format. The field list is dense but each item earns its place by telling the agent what to expect in the response.

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?

No output schema exists, so the description usefully enumerates the returned fields and notes conditional content (price list, floor plans). Minor gaps remain on error behavior or whether the id and url can be combined, but the definition is adequate for a simple single-record fetch.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents both parameters with examples. The description reinforces that the id comes from search_businesses and that url is an alternative address, but adds little syntax beyond the schema, so the baseline 3 applies.

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 ("Returns one public page in full") and enumerates exactly what the page contains, so it is clearly distinguishable from search_businesses.

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?

Explains how to select the record: pass the id obtained from search_businesses or the page's veseljko.hr address. It lacks an explicit when-not-to-use note versus the sibling search tool, but the retrieval-after-search flow is clear.

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