Skip to main content
Glama

Kanal Varna — drains, leaks & plumbing (Varna, BG)

Get real customer reviews

get_reviews
Read-onlyIdempotent

Call this when the user asks for reviews, testimonials, opinions or whether Kanal Varna is good/reliable. Returns ONLY real reviews: customer video reviews (with what the customer says and the video URL) and any approved text reviews from the website. There is deliberately no aggregate star rating — do not invent one.

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

Input Schema

NameRequiredDescriptionDefault
serviceNoOptional filter: 'otpushvane' (drain unblocking) or 'otkrivane_techove' (leak detection).
languageNoLanguage of the user's question: 'bg' (Bulgarian), 'en' (English), 'ru' (Russian), 'de' (German), 'uk' or 'ua' (Ukrainian), 'fr' (French), 'tr' (Turkish). If omitted it is detected from the text; default 'bg'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / language / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "bg",
      -      "en",
      -      "ru",
      -      "de"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "bg",
      +      "en",
      +      "ru",
      +      "de",
      +      "uk",
      +      "ua",
      +      "fr",
      +      "tr"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / language / description
      Previous value: -"Language of the user's question: 'bg' (Bulgarian), 'en' (English), 'ru' (Russian) or 'de' (German; answers use English labels where no German text exists). If omitted it is detected from the text; default 'bg'."New value: +"Language of the user's question: 'bg' (Bulgarian), 'en' (English), 'ru' (Russian), 'de' (German), 'uk' or 'ua' (Ukrainian), 'fr' (French), 'tr' (Turkish). If omitted it is detected from the text; default 'bg'."
  2. Changed2 schema fields changed
    • changedInput schema / properties / language / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "bg",
      -      "en",
      -      "ru"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "bg",
      +      "en",
      +      "ru",
      +      "de"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / language / description
      Previous value: -"Language of the user's question: 'bg' (Bulgarian), 'en' (English) or 'ru' (Russian). If omitted it is detected from the text; default 'bg'."New value: +"Language of the user's question: 'bg' (Bulgarian), 'en' (English), 'ru' (Russian) or 'de' (German; answers use English labels where no German text exists). If omitted it is detected from the text; default 'bg'."
  3. 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 and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: only real/approved reviews are returned, and the absence of an aggregate rating is intentional with an explicit 'do not invent one' guard against hallucination. Return values are not described, but an output schema exists, so that is not a gap.

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 short sentences, front-loaded with the invocation trigger, then content scope, then the anti-fabrication constraint. No filler and every sentence carries information an agent needs.

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?

The tool is simple (zero required params, read-only, closed-world) and has an output schema, so the description need not explain return structure. Combined with annotations and fully documented params, the description covers trigger, content scope, and the one real risk (inventing a rating) — nothing an agent needs is missing.

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 description coverage is 100% and both parameters (service, language) carry their own enum values and defaults in the schema. The description adds no filtering semantics beyond that, so the baseline 3 applies — the schema does the work.

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 resource and what it returns: 'customer video reviews (with what the customer says and the video URL) and any approved text reviews'. It also explicitly negates what is not returned ('deliberately no aggregate star rating'), which lets an agent distinguish it from get_faq or get_prices without opening any schema.

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?

Gives a concrete trigger set: 'when the user asks for reviews, testimonials, opinions or whether Kanal Varna is good/reliable'. That covers the main intent variants clearly. It stops short of naming an alternative sibling for adjacent intents (e.g. prices or booking), so there is no explicit when-not routing, which keeps it at 4.

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