Skip to main content
Glama

Official dealer for a country

dealer_for_country
Read-onlyIdempotent

Finds the official Vargov®Design dealer, contact page, and published installation terms for a specified country or city; omit location to return all regional dealers.

Instructions

Who supplies, installs and services Vargov®Design compositions in a given country: the official dealer of that region (Moscow — Russia and the CIS; Hanoi — Vietnam, Laos, Cambodia, Thailand, Malaysia, Singapore; Dubai — the Persian Gulf, Middle East, Americas, Europe, Asia, Africa and every other country), the page with the dealer contacts, the brand's direct contacts, and the installation terms as published (a separate service priced individually; supervised installation available). country: a country name in English or Russian, an ISO 3166 alpha-2 code, or a major city (Dubai, Moscow, Hanoi…). Without country, returns all three regions.

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

Input Schema

NameRequiredDescriptionDefault
langNoen (default) or ru
countryNoe.g. "United Arab Emirates", "UAE", "AE", "ОАЭ", "Dubai", "Казахстан"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the three regional dealer hubs with their coverage areas, the fact that the response includes contact pages, direct brand contacts and published installation terms, and that installation is a separately priced service. It does not say what happens when no dealer covers a country, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening clause is well front-loaded and the default-behavior sentence is efficient. But the long parenthetical enumerating every covered territory for Moscow, Hanoi and Dubai is bulky and mostly irrelevant to the decision to call the tool, weighing the sentence down without adding actionable signal.

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-required-parameter, read-only lookup with no output schema, the description is largely complete: it explains the input formats, the no-parameter default, and what content the response carries. The only meaningful gap is the empty-result case, where an unknown country or uncovered region is not addressed.

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 already lists example country values, so the baseline is 3. The description still adds meaning beyond the schema: it states the country parameter accepts English or Russian names, ISO 3166 alpha-2 codes, or a major city, and it explains the consequence of omitting country entirely (all three regions returned), which the schema cannot convey.

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?

The description opens with a specific verb-and-resource statement: it returns who supplies, installs and services the brand's compositions for a given country, along with dealer contacts, brand direct contacts and installation terms. That is far more than a restatement of the name 'dealer_for_country' and lets an agent distinguish it from brand_facts or get_composition without opening a schema.

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

Usage Guidelines3/5

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

The description gives a clear default behavior ('Without country, returns all three regions'), which is real usage guidance for the optional parameter. However, it never states when to prefer this tool over the sibling tools such as brand_facts, nor any exclusions or prerequisites, so the guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.