Skip to main content
Glama

Wafergraph MCP

by com.wafergraph

Compare countries

compare_countries

Side-by-side comparison of 2-5 countries: aligned rows for company count, segment mix, market-position mix, and priced market cap, plus which segments each country is uniquely present in or dominant in, and which segments they all share. country is the company's HEADQUARTERS country only, not a manufacturing-footprint field. A company headquartered here may fabricate, assemble, or test elsewhere — do not read this data as production geography.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countriesYes2-5 country names, e.g. ['Taiwan','South Korea','United States']. Case-insensitive; common short forms recognized.

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It explicitly clarifies that 'country' means headquarters only not production geography, and describes output structure. This is valuable beyond what schema provides.

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

Conciseness4/5

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

The description is five sentences, each adding value. The first sentence fronts the purpose. One sentence is a critical caveat. Minor redundancy could be trimmed but overall efficient.

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 description covers output format, key behavioral nuance (headquarters vs production), and parameter constraints. No output schema exists, but the description compensates sufficiently. Complete for a single-parameter tool.

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% for the single parameter, so baseline is 3. The description adds no new parameter-level details beyond what the schema already states about format and case-insensitivity.

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?

Description starts with 'Side-by-side comparison of 2-5 countries' which specifies the verb and resource, then lists specific output fields (company count, segment mix, etc.), clearly distinguishing it from sibling tools like compare_companies or get_country_profile.

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

Usage Guidelines2/5

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

No mention of when to use this tool vs alternatives. The description does not compare with siblings or provide context on when this is preferred over get_country_exposure or list_countries.

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

All Wafergraph MCP 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.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: analyzing portfolio exposure, comparing companies, finding chokepoints, getting company details, country exposure, deals, segments, supply chain walk, and company search. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., 'get_company', 'search_companies', 'find_chokepoints'). The convention is uniform and predictable.

Tool Count5/5

9 tools is well-scoped for a specialized supply chain analysis server. Each tool serves a distinct query or analysis need without being too few or too many.

Completeness4/5

The tool set covers core operations: search, detail, comparison, portfolio analysis, chokepoint identification, country exposure, deals, and supply chain graph traversal. Minor gaps like historical trends or alerts exist but do not hinder primary use cases.

Resources