Skip to main content
Glama

Tonzar B2B Russian Export Marketplace

by io.github.introman2023

searchProducts

Search the Tonzar B2B catalog of 160,000+ Russian industrial, medical, and agricultural products. Returns matching products with prices, suppliers, and specs. Use for finding Russian equipment for export.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (product name, type, or keyword). English or Russian.
excludeNoExclude products containing these terms in name, description or specs. Comma-separated for multiple (e.g. "chipboard,ЛДСП"). Also supports minus syntax in query itself (e.g. query "desk MDF -chipboard").
categoryNoOptional category filter (e.g. "Medical", "Industrial", "Transport")
maxResultsNoMax results to return (1-50, default 10)

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided. Description lacks behavioral details such as rate limits, authentication needs, read-only nature, pagination, or sorting behavior. Only states what is returned, not side effects or constraints.

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 concise sentences with front-loaded purpose. No redundant information. Every sentence adds value.

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?

Adequately describes tool purpose and output (prices, suppliers, specs). Missing output schema and annotations, but description compensates well. Could mention search behavior (e.g., fuzzy vs exact) or multilingual handling.

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% with clear parameter descriptions. Description adds minimal extra value beyond schema (e.g., catalog scale, result content). Baseline is appropriate.

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?

Clearly states verb (search), resource (Tonzar B2B catalog of Russian products), and expected returns (prices, suppliers, specs). Differentiates from siblings like getProduct (single product) and listCategories.

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 states use case: finding Russian equipment for export. Implicitly distinguishes from siblings (getProduct for specific item, listCategories for browsing). Could be more explicit about when not to use.

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

All Tonzar B2B Russian Export Marketplace toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct operation: getting a product, getting a supplier, listing categories, listing products in a category, and searching. No overlap in purpose.

Naming Consistency5/5

All tool names use a consistent verb_noun pattern in camelCase (getProduct, getSupplier, listCategories, listProducts, searchProducts).

Tool Count5/5

Five tools is well-scoped for a read-only B2B catalog, covering browsing, searching, and detailed views without excess.

Completeness5/5

The tool set covers the full user journey: browse categories, list products, search, get product details, and get supplier details. No obvious gaps for the intended read-only use.

Resources