Skip to main content
Glama
AiAgentKarl

supply-chain-mcp-server

search_suppliers_by_country

Search for manufacturers and suppliers in a specific country using Open Supply Hub data. Filter by optional sector to narrow results.

Instructions

Sucht Fabrikanten/Lieferanten in einem Land via Open Supply Hub.

Args: country: Land (z.B. "Bangladesh", "Vietnam", "India", "China") sector: Branche (z.B. "apparel", "electronics", "footwear") — optional limit: Anzahl Ergebnisse

Returns: Liste von Lieferanten/Fabriken mit Standorten

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes
sectorNo
limitNo
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool searches and returns a list, but lacks details on behavioral traits such as data freshness, rate limits, error handling, or pagination behavior. The description is minimal in this regard.

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?

The description is concise and well-structured: a single purpose sentence, followed by organized Args list, then Returns. Every sentence adds value. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description mentions returns a list of suppliers with locations but lacks detail on the structure of each supplier entry. It also does not cover pagination or maximum limits. For a simple search tool, it is adequate but not fully comprehensive.

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 description coverage is 0%, so the description must compensate. It provides clear explanations for all parameters: country with examples, sector with examples and optionality, limit with meaning. This adds meaningful context beyond the schema.

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 clearly states it searches for manufacturers/suppliers in a country via Open Supply Hub. The verb 'Sucht' (searches) and resource 'Fabrikanten/Lieferanten' are specific, and it distinguishes from sibling tools which focus on trade statistics and risks.

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 provides basic context (via Open Supply Hub) but does not explicitly state when to use this tool versus alternatives like get_country_trade_stats or get_supply_chain_risk. No when-not-to-use guidance is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AiAgentKarl/supply-chain-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server