Skip to main content
Glama

Brand card

brand_facts
Read-onlyIdempotent

Retrieve a compact company profile for Vargov®Design covering founder, catalogue, awards, certification, contacts, dealers, configurator scope and dataset links; figures are computed from bundled data.

Instructions

Compact card of Vargov®Design: founder and founding year, catalogue size and families, configurator scope (full calculation, 1:1 drawing), the awards count and list, certification, trademarks, showroom, contacts, dealers page, site languages, links to llms.txt of the site, the knowledge base and the configurator, the open dataset on Hugging Face. Numbers are computed from the bundled data.

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

Input Schema

NameRequiredDescriptionDefault
langNoen (default) or ru for the wording fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld=false, so the safety profile is covered. The description adds genuinely useful context beyond that: 'Numbers are computed from the bundled data,' signalling a static, self-contained snapshot rather than a live lookup, and it discloses that the card is link-heavy (llms.txt, knowledge base, Hugging Face dataset).

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?

It is one very long run-on sentence with roughly twenty comma-separated items, which is dense to parse. The leading 'Compact card of Vargov®Design:' front-loads the subject well and most items do convey what the agent will receive, but the enumeration could be grouped or trimmed.

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?

With no output schema, the description bears the burden of describing return contents and does so thoroughly. The one remaining gap is that it never explains the `lang` parameter's effect on returned wording, which matters for a localized card.

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?

There is a single optional `lang` parameter with 100% schema description coverage and an enum, so the schema already carries the semantics. The description does not mention `lang` or explain that it switches the wording fields between en and ru, adding nothing beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this returns a 'compact card of Vargov®Design' and enumerates exactly what the card contains (founder, catalogue size, awards, certifications, showroom, links to llms.txt/dataset, etc.). That is specific enough to distinguish it from siblings like get_composition or dealer_for_country, though it never explicitly names an alternative.

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?

Usage is only implied: the enumerated contents suggest it is the go-to for general brand/company overview questions. There is no explicit when-to-use statement, no exclusions, and no pointer to siblings such as dealer_for_country even though a 'dealers page' is mentioned as card content.

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